Fix git merge --continue missing --no-edit in Rebuild workflow#3459
Draft
Fix git merge --continue missing --no-edit in Rebuild workflow#3459
git merge --continue missing --no-edit in Rebuild workflow#3459Conversation
…ontinue Co-authored-by: henrymercer <14129055+henrymercer@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix failing GitHub Actions workflow Rebuild Action
Fix Feb 4, 2026
git merge --continue missing --no-edit in Rebuild workflow
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 Rebuild Action workflow fails when
git merge --continueruns in a non-interactive environment without a commit message flag.Changes
Added
--no-editflag togit merge --continueon line 114 of.github/workflows/rebuild.yml:This aligns with the existing pattern on line 100 where the same flag is used for merge commits.
Risk assessment
Low risk: Workflow-only change affecting internal automation.
Which use cases does this change impact?
Workflow types:
Products:
Environments:
How did/will you validate this change?
If something goes wrong after this change is released, what are the mitigation and rollback strategies?
How will you know if something goes wrong after this change is released?
Are there any special considerations for merging or releasing this change?
Merge / deployment checklist
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.