-
Notifications
You must be signed in to change notification settings - Fork 5
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
Does a tree have to be pushed? #25
Comments
Hi @ericclemmons, Nice observation. At first, I didn't want to push the branch, but I had some issues. Example: I created a test branch from the master without pushing it.
My solution was to add the push command while adding the worktree. I can configure it for the user based on an environment variable, ===== However, I can't understand your point about reviewing a PR. ===== Please let me know what you think. |
@alexiszamanidis |
Hi @zcfan, I truly appreciate your suggestion. In regard to this feature, I'd like to gather your insight on whether you envision it being enabled by default or requiring users to manually turn it on. From my perspective, having it enabled by default seems logical. This way, when users attempt their initial push, it could potentially preempt the error scenario you mentioned by ensuring their local repository is up to date with the remote repository. Your thoughts on this aspect would be valuable as we move forward with refining this feature. Thank you once again for your valuable contribution and engagement with the project. Looking forward to your insights! |
@alexiszamanidis I prefer not to auto pull/push by default, since it's the default behavior of But previous versions of your extension is auto by default, and it has so many users already!🎉 So keep consistent is also acceptable. Personally I perfer not to auto pull/push, because the repo I'm working on is messy, remote commits might break my local workspace accidentally. |
@zcfan |
Hi @zcfan, I am glad to inform you that the options have been added. Please take a moment to check them out and provide valuable feedback on the work. I apologize for any delay in implementing these changes - I was in a bit of a rush. Looking forward to hearing your thoughts! |
@alexiszamanidis Work like a charm, thank you! |
Glad you like it! |
When reviewing PRs for an org's repo, I don't have explicit
git push
permissions, only to my fork.So I can't
add
a worktree because the command fails creating it (and then pushing it)The text was updated successfully, but these errors were encountered: