Skip to content
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

GitFlow: Error during work with local branches only #53

Closed
YanumVlad opened this issue Feb 11, 2019 · 6 comments
Closed

GitFlow: Error during work with local branches only #53

YanumVlad opened this issue Feb 11, 2019 · 6 comments
Assignees

Comments

@YanumVlad
Copy link

I play with addin with local branches only.
GitFlow's Start New Feature fails with:

git checkout develop
Already on 'develop'
git pull
There is no tracking information for the current branch.
Please specify which branch you want to merge with.
See git-pull(1) for details.
git pull
If you wish to set tracking information for this branch you can do so with:
git branch --set-upstream-to=/ develop

Error (405 ms @ 2/12/2019 1:35:18 AM)

I have no remote branches, in addition - I did not find way on how to prevent Pull issuing.

Thanks,
Vlad

@sboulema
Copy link
Owner

Grab the new release!

Go to Tools -> Options -> TGit -> [] Pull changes

@YanumVlad
Copy link
Author

Glad to hear :))
Unfortunately, I tried to update extension via Visual Studio. Update even did not start: just 1-second show of download dialog and the subsequent closure...
Could you please take a look? :)

@sboulema
Copy link
Owner

Try updating using the vsix file: https://github.com/sboulema/TGit/releases/download/v4.11.58/TGit_4.11.58.vsix

Download and open should start installation.

@YanumVlad
Copy link
Author

Great!!! Now it works. Thank you very much for so quick response!!

Just as a minor comment, I just noticed the next spelling issue in final line (Succes with sinlge S at the end):

git checkout develop
Already on 'develop'
git checkout -b feature/Feature4 develop
Switched to a new branch 'feature/Feature4'

Succes (365 ms @ 2/12/2019 1:55:43 PM)

It would be nice to fix as well, if you have time :)

@sboulema
Copy link
Owner

Great to hear!

Wow that spelling issue has gone unnoticed since 2015...

Grab the new release! 🚀

@YanumVlad
Copy link
Author

Excellent! Good job! Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants