Restrict Production/Release dispatch to main#124
Open
bschwedler wants to merge 1 commit into
Open
Conversation
Add a main-only gate job so manually dispatching Production or Release from a non-main branch fails immediately instead of running a full build, or, for Release, branching and opening a release PR off the wrong ref. Reusable-workflow caller jobs (uses:) can't carry `environment:` directly, so the check lives in its own job that build/release depend on via needs:. The production GitHub environment in this repo now has a branch policy restricting deploys to main.
bschwedler
requested review from
CDRayn,
ianpittwood and
jmwoliver
as code owners
July 15, 2026 18:10
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Manually dispatching Production or Release from a non-main branch runs the full build, or for Release, opens a release PR, with no ref check — Production only skips the final push step, and Release has no guard at all.
Adds a
main-onlygate job backed by this repo'sproductionGitHub environment, now restricted to themainbranch.build/releasedepend on it vianeeds:, so an off-main dispatch fails immediately instead of burning CI time or mutating repo state from the wrong ref.This lives in its own job because a job that
uses:a reusable workflow can't also carryenvironment:.