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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,456,637
Community Members
 
Community Events
176
Community Groups

Mandatory scopes for a GitHub Oauth token

Hi.

I use GitHub and Sourcetree and I switched from using a simple username and password identification to work on my repos (which is now deprecated) to using personal access tokens. When managing a token in GitHub I can choose his scope. I'm not that familiar with all the options and don't want to give access to unnecessary stuff so I choose only "repo" and "delete_repo". But this token doesn't work when using it as a password in Sourcetree. If I create a token that give access to everything, now the token works.

So I clearly need to give at least some additional scope to my token than just the "repo" and "delete_repo" but I don't have a clue which ones. I did not find any documentation on this, which is odd.

Can you help me with that? Thanks.

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events