Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How to modify GitHub OAuth scopes requested?

Our enterprise just switched from BitBucket to GitHub Enterprise (hosted). I have access to several orgs inside the enterprise. When attempting to add the GitHub account to SourceTree I have two options (GitHub and GitHub Enterprise) but only one, GitHub, allows me to use OAuth. When using OAuth and clicking 'refresh token', a browser tab opens (github already logged in and PAT already created) asking me if I want to add SourceTree as a trusted app. All is well so far, but in the list of orgs that I belong to, only one is checked (not the one I really need) and the rest have an 'authorize' button next to them. Clicking the 'authorize' button it tells me that I'm about to ask the owners for permission. Well, I take a look at all the permissions (scopes) that SourceTree is asking for and I know full well they'll never allow it. So, now to my question...

Why does SourceTree ask for so many (seemingly all) permissions/scopes from GitHub? Is there a way to modify the scopes being requested?

0 answers

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events