Fix evergreen agent "Branch does not exist locally" push failure#79
Merged
Conversation
…re push The push_to_pull_request_branch tool requires a named local branch to create patches from. When the agent checks out the PR branch with a detached HEAD, the tool fails with "Branch does not exist locally". Updated step 2 of the agent instructions to explicitly use `git checkout -b` to create a local tracking branch. Agent-Logs-Url: https://github.com/githubnext/tsessebe/sessions/d2700d0e-7bbb-4650-aa27-84a4b45b7c29 Co-authored-by: mrjf <180956+mrjf@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix evergreen failing to merge due to tool failure
Fix evergreen agent "Branch does not exist locally" push failure
Apr 8, 2026
mrjf
marked this pull request as ready for review
April 8, 2026 19:51
Contributor
|
@copilot you must recompile to change evergreen job with gh aw compile |
Contributor
Author
Ran |
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 evergreen agent was failing to push merge conflict resolutions with
push_to_pull_request_branchreturning "Branch does not exist locally". This happened ~20+ times on PR #58 because the agent would check out the PR branch as a detached HEAD, which the push tool cannot create patches from.evergreen.mdstep 2 to require a named local tracking branch:Note: The earlier "protected files" push failures were separately fixed by PR #75 (
protected-files: allowed). This addresses the remaining failure mode.