-
Notifications
You must be signed in to change notification settings - Fork 9
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
git config branch.autosetupmerge: always is not optimal #19
Comments
Hi Shaun! It was mostly due to convenience since most people have repositories on the origin before using strap. What would be the repercussions of removing the line? |
The repercussion would be that the user would have to use The way I look at it, if you don't have a remote branch already, |
Hi there,
https://github.com/strapsh/strap/blob/master/cmd/run#L193 has [may be] unintended consequences. In simple workflows that use a local branch with a remote branch of the same name, having
autosetupmerge
requires that the branch be created on the remote first (or always use--no-track
with agit branch
command).I'm curious about the motivation for having this set and whether you would be willing to remove this setting if I created a PR for it.
The text was updated successfully, but these errors were encountered: