You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Mac OS X 10.12.6 / SourceTree 2.7.6
I have a repo at github. I've created a clone on my laptop. On GitHub I created a Personal Access Token and assigned all the scopes.
In SourceTree I open Preferences, click Accounts, click the GitHub account, click Edit and past the PAT into the password field. It appears to accept that.
I then click Push ... and I get this:
git -c diff.mnemonicprefix=false -c core.quotepath=false -c credential.helper=sourcetree push -v --tags origin refs/heads/master:refs/heads/master
Pushing to https://github.com/ericscheid/homebrewery
remote: Invalid username or password.
fatal: Authentication failed for 'https://github.com/ericscheid/homebrewery/'
(etc)
Completed with errors, see above.
Where am I going wrong?
Hi, did you find any solution to this problem? I'm facing the same issue
Thanks!
Just in case any of you are still looking for an answer, I finally ended up doing the following:
1- Go to "C:\Users\USER\AppData\Local\Atlassian\SourceTree"
2- Delete the file passwd
3- Open Sourcetree and make some action in the repository (push, fetch, pull)
4- Sourcetree is going to request the password and we are going to enter the PAT
5- Enjoy!
Apparently Sourcetree keeps an old version of the password in that file and doesn't replace it when we change it in the Tools -> Options -> Authentication.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can also check answers to this related question (and maybe more particularly this one). In addition, an interesting summary of procedures can be found on Stack Overflow.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.