SourceTree keeps creating new Personal Access Tokens on my GitHub account!

I use GitHub with 2FA.  In previous versions of SourceTree, I could go into my GitHub Account and create a Personal Access Token and use that as my password, and all was good in the world.  Now, with version 2.0.20.1, SourceTree will not accept the Personal Access Token that I generate myself, and it seems to keep generating new ones automatically on my GitHub account and keeps repeatedly asking for me to re-login with 2FA.  Each time I do, it seems, it creates another new Personal Access Token.

For example, every time I switch from my wired connection to wireless, SourceTree pops up a GitHub login, where I enter my usual username and password then the 2FA code sent to my phone.  It seems like every time it does this, it creates a brand new Personal Access Token in my GitHub account - totally defeating the purpose!

Under Tools --> Options --> Authentication, SourceTree has created its own "github.com" entry for me with Username: Personal Access Token.  I tried to delete that one and set up my own, using Basic Authentication, with my usual github username and a Personal Access Token I manually generate myself as the password, and it will not connect with those credentials.  It seems the only way it will connect to github is through the Account it creates itself after the github login popup screen - the one that keeps creating new Personal Access Tokens each time.

Very frustrating and particularly annoying since I pay for each of those texts to send the 2FA code to my phone.

2 answers

1 accepted

0 vote
Mike Corsaro Atlassian Team Jun 14, 2017

Hello! I'd highly recommend that you use the OAuth feature for GitHub accounts -- it's much easier to setup and works much better. When adding a new account, just select the OAuth option, and hit the "Refresh OAuth Token" button.

Thanks! OAuth solved the problem for me but it required a restart of the app after authorising. It also did not help that after redirecting back to localhost there was an error in the browser - I thought the OAuth flow failed.

Mike Corsaro Atlassian Team Jun 16, 2017

Glad I could help! Sometimes that happens -- it's currently a known bug.

The problem seems to have resolved itself when I updated to version 2.1.2.5

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published May 30, 2018 in Sourcetree

Tip from the team: configuring Git or Mercurial in Sourcetree

Supported Platforms macOS Windows To make using Sourcetree as simple yet powerful as possible we embed (bundle) dependencies such as Git, Git LFS, and Mercurial. We strive to keep these...

573 views 1 2
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you