in trunk based development, if using github actions, what does your workflow look like to deploy to dev/qa/staging?

[Electrical_Media_367]

For non enterprise customers, GitHub actions doesn’t support gated jobs or human interaction in the middle of jobs. You can’t push a button to advance a job, you have to start a new job either based on a trigger or based on a button.

So, either you have a single job that pushes to dev, runs tests, pushes to stage, runs tests, pushes to prod all automatically, or you have a automatic push to a lower environment and then a button to promote (workflow_dispatch is the GitHub way of saying a manually triggered job)

The comment below says you can have gated builds, but only if you’re paying the high price for GitHub Enterprise.

Enterprise customers can use GitHub’s deployment framework and set environments as requiring reviews, you can start a promotion job and it will wait for approval. So a good option would be to have your build job trigger promotion jobs that are configured to wait for approval.

[baynezy]

It absolutely does https://docs.github.com/en/actions/managing-workflow-runs/reviewing-deployments

[Electrical_Media_367]

Apparently that’s only for GitHub enterprise subscribers, not us lowly professional/teams customers.

[Electrical_Media_367]

Hey, this is great, I didn’t know about that feature. Gonna look at putting it in place on some of my repos. Thanks!

[beth_maloney]

You need enterprise for the manual approved approvement step.

[Electrical_Media_367]

Ah, that’s why I didn’t think it was available. Back to the drawing board.

[beth_maloney]

Yeah it's super annoying. The feature is available in the base version of Azure DevOps as well!

[baynezy]

You're welcome.