Policy: Allow opted-in draft workflow pin refreshes - #96
Merged
Merged
Conversation
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.
This proposes a narrow standing authorization for preparing fleet-managed CI and release caller pin refreshes in repositories that explicitly opt in. The local diff must be limited to the existing reusable-workflow SHA pins, and the target central commit and old-to-new workflow behavior must be checked before pushing.
The proposal does not authorize marking a PR ready, merging it, or publishing a release. It also does not opt in any plugin repository or change the synchronizer. Those remain separate decisions. The organization validation suite passes.