fix: respect repo default branch #1270
Closed
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
Contributor
|
All contributors have signed the CLA ✍️ ✅ |
Author
|
I have read the CLA Document and I hereby sign the CLA |
Collaborator
|
Thanks for the contribution, and apologies for the slow response. We've received many PRs, and we don't have the bandwidth on the codex team to review all of them. Is there a bug filed for this issue? If so, could you please link it? If not, please open one and describe the problem in more detail. This will help us prioritize. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description of bug
-When connecting a GitHub repo to Codex, setup fails with the error:
-Provided git ref master does not exist
Expected behavior
Codex should:
• Detect the repo’s actual default branch (usually main)
• Or allow selecting the desired Git ref during setup
• Or provide a more helpful error suggesting that master is missing
Additional context
GitHub changed the default branch from master to main in 2020. Many tools now use main as standard, and hardcoding a master ref leads to unnecessary setup failures.