Use recovery credentials for the automatic rollback push - #209
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.
The automatic rollback after PR205 pushed its revert successfully, but no required push-event CI appeared. The recovery command supplied its dedicated token in the Git URL while actions/checkout had already installed a GITHUB_TOKEN Authorization header. Git uses that inherited header, so the push succeeds under the wrong identity and GitHub suppresses downstream push events.
Clear that header for the recovery push only, allowing the existing recovery token to authenticate the command. Normal checkout authentication, credential scopes, required checks, merge protection and recovery decisions remain unchanged.
Validation: a real local Git HTTP push using invented credentials reproduces the original behavior, then executes the workflow's corrected push command and verifies the recovery identity, created branch and preserved checkout configuration. The regression fails on the original command. All 20 focused release/recovery tests pass. No real credentials were inspected or rotated, and no production rollback was induced; the token's live validity and complete rollback path remain unverified until exercised.