Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings
Discussion options

Select Topic Area

Bug

Body

I tried to switch from classic tokens to fine grained api tokens.

I created a token, with limited access, only on repositories of one organisation, and added some private repositories that this token should see.

But as I save and double checked the result, the token permission was changed to "only public repositories".

I made multiple tries to create a new token or update the existing token to grant acces for my private repositories.
But it seems that the token is never saved with my selected config in "Repository access" section is not saved, instead it is always saved with only "public repository" access.

What can I do?
Or how long it will take until this problem is fixed?

You must be logged in to vote

Replies: 2 comments

Comment options

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

  • Your input will be carefully reviewed and cataloged by members of our product teams. 
    • Due to the high volume of submissions, we may not always be able to provide individual responses.
    • Rest assured, your feedback will help chart our course for product improvements.
  • Other users may engage with your post, sharing their own perspectives or experiences. 
  • GitHub staff may reach out for further clarification or insight. 
    • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

  • Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
  • Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

  • Upvote and comment on other user feedback Discussions that resonate with you.
  • Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

You must be logged in to vote
0 replies
Comment options

After some research I found out that some people recomment to choose "contents" in the permission dropdown, but in my case I dont have a permission name "content" or "repo" in my permission selection dropdown

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug GitHub or a GitHub feature is not working as intended API and Webhooks Discussions related to GitHub's APIs or Webhooks
1 participant
Morty Proxy This is a proxified and sanitized view of the page, visit original site.