fix(release): fast-forward bootstrap branch - #33
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR fixes the release workflow’s bootstrap push behavior when the release branch ref is created via the GitHub API after the runner’s checkout, avoiding a --force-with-lease rejection caused by missing local tracking state.
Changes:
- Replace
git push --force-with-leasewith a standard fast-forwardgit pushfor the initial push to the API-created release branch. - Add inline rationale explaining why an ordinary push is safe in this specific scenario.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
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.
The release workflow creates a protected release branch through the GitHub API. Its next push used a lease without a local tracking value and therefore rejected the workflow's own new ref. Use an ordinary fast-forward push: it succeeds from the declared release base and still rejects unexpected remote advancement.