Fix Scoop manifest push rejected by branch protection - #18
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The update-scoop release job pushes the generated bucket/agentflare.json directly to master, which the required-status-checks protection rejects (GH006) when authenticated as the default GITHUB_TOKEN — this killed the Update Scoop job on every release run so far (v1.0.0 x2, v1.0.1). Checkout now uses the owner's CLA_SIGNATURES_TOKEN PAT (enforce_admins is off, so the admin-authenticated push clears protection). Also renames the step, which still said 'push to main'.