Skip to content

Change CI to always deploy via workflow trigger #277

@JobDoesburg

Description

@JobDoesburg

Right now we deploy on the following moments:

  • automatically on push to master, to staging env
  • via workflow_dispatch on master, to production env
  • via responding deploy on a PR, to develop

I propose to do the following:

  • automatically on push to master, to staging env
  • via workflow_dispatch on any branch, to any env

This way, we can have multiple branches active and allow them all to be deployed to master if we want it. I think that for the purpose of this project, where we sometimes might want to make changes to thadmin for a specific event, this is desirable. Github offers a nice UI for this, too (when triggering a workflow, you can specify the branch you want to use, and you can select multiple env's to deploy to)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions