[NO-ISSUE] ci: run governance once per commit (drop push trigger on dev) - #771
Merged
Merged
Conversation
isaquebock
approved these changes
Jul 21, 2026
herbert-julio-azion
approved these changes
Jul 21, 2026
rafaelgarbinatto
approved these changes
Jul 21, 2026
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
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.
Summary
Every commit landing on
devcurrently runs the Governance Pipeline twice: once viapushondevand once viapull_requestsynchronize on the standingdev→mainrelease PR (see the duplicated checks on #768). This dropsdevfrom thepushtrigger so each commit is validated once.pull_request: [main, dev]stays — it feeds the required status checks for feature PRs and for the release PR, and validates the merge ref.push: [main]stays — post-merge sanity run onmain(fires with the release PR already closed, so it never duplicates).Notes
governance.ymlbranch ongithub.event_name/github.ref, so nothing depended on the push-on-dev run.citype → no version bump.dev(outside a PR, with no open release PR) would skip governance; the repo flow is PR-only, and "require branch up to date" ondevcovers the stale-merge gap.