[DEV-74] Avoid failed master branch lookups when the repository uses main - #18
Merged
Conversation
added 2 commits
August 19, 2026 10:31
![devintern-internal[bot]](https://github.githubassets.com/images/gravatars/gravatar-user-420.png){kind=avatar}
…repository uses main
Fetch newly discovered remote default branches before creating local tracking branches, with integration coverage for a master-to-main default change. Bound the authoritative remote HEAD probe, disable interactive Git/SSH prompts, and verify cached origin/HEAD fallback on probe failure. Iteration 2: address additional review feedback Iteration 3: address additional review feedback Iteration 4: address additional review feedback Iteration 5: address additional review feedback
2 tasks
3 tasks
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.
Task: DEV-74
Summary: Avoid failed master branch lookups when the repository uses main
Implementation Details
Repository automations no longer assume the primary branch is
masterand then fail over tomainafter several Git errors.mainimmediately when that is the repository default; keepmasterand other configured defaults working.origin/HEADas an offline fallback when a live probe cannot run.master→mainrename).main,master, custom defaults, and a remote default-branch change.This removes the noisy
couldn't find remote ref master/pathspec 'master' did not matchsequence from cron and JQL-driven workflows on repositories whose default branch ismain.This PR was automatically created by @devintern/code