Repository navigation
fix: plan governance once per organization - #28
Merged
Merged
Conversation
Signed-off-by: Vitor Mattos <1079143+vitormattos@users.noreply.github.com>
Signed-off-by: Vitor Mattos <1079143+vitormattos@users.noreply.github.com>
vitormattos
force-pushed
the
fix/organization-governance-workflow-20261022
branch
from
October 22, 2026 17:09
b65b1c6 to
4c55ee1
Compare
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
Cause
The previous workflow created a protected job for each repository, which resulted in dozens of pending environment approvals. The dry-run also treated expected drift as exit code 1, making every repository job red until an independently authorized apply.
Dependency and rollout
Depends on LibreCodeCoop/github-governance#36. This PR pins the reviewed signed commit from that PR, rather than an unpinned branch. Merge/verify the upstream PR first. After an upstream tagged release, update the SHA plus version comment for automated dependency tracking.
This PR does not run or approve a privileged governance apply. The private key is unchanged and remains environment-scoped; plans still require a single environment approval.
Validation
Security tradeoff
The apply token is installation-scoped across the organization's installed repositories, not repository-scoped like the old matrix token. This is required by the existing organization-level CLI and is gated by ruleset-sync review and explicit manual apply. No broader GitHub App installation permissions were introduced.