-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for default branch names other than master
#87
Comments
Just ran into this bug:
It wasn't obvious that the problem were with remote branch name |
I have a fix for the basic case ( AFAIK, the proposal for a standard way for a repository to signal that a branch has been renamed never went anywhere, and in any case, supporting that in Braid would be a low priority for me, so I'll declare it out of scope of this issue. |
Released in Braid 1.1.8. After so much work on infrastructure for future maintainability, it's fun to deliver a small feature for a change. |
We are about to start seeing a lot more git repositories being created with default branch names other than
master
or renaming their default branch away frommaster
. At a minimum,braid add
with no branch, tag, or revision specified should use the default branch of the upstream repository (as given by its HEAD symref) rather than hard-codingmaster
.If, in the future, there is a standard way for the upstream repository of an existing mirror to indicate that the branch used by the mirror has been renamed (currently under discussion), Braid could offer to update its configuration. This would mainly be for cleanliness, as it sounds like the plan is that the old name would continue to work. There is probably no need for Braid to have a new mirror mode that automatically follows the upstream default branch as given by the HEAD symref; it doesn't sound like other tools are planning to take that approach.
The text was updated successfully, but these errors were encountered: