Replies: 3 comments
-
|
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
Beta Was this translation helpful? Give feedback.
This comment was marked as low quality.
This comment was marked as low quality.
-
This may be an org/enterprise policy issue, not the token form itselfI ran into something similar before, and the confusing part is that the organization dropdown is not simply "all orgs I belong to". For fine-grained PATs, GitHub only shows organizations that can actually be selected as the token's resource owner. If an organization or enterprise has blocked fine-grained PAT access, that org may not appear in the selector at all. A few things I would check:
The UI could definitely explain this better. Right now it can feel like GitHub is just failing to load organizations, when the real reason might be policy/permission related. For the auto-rotation sideI would be careful with a workflow that depends on repeatedly recreating PATs. PATs are pretty awkward for machine automation, especially when org approval, SSO, expiration policies, and fine-grained limitations get involved. If this is for automation, a GitHub App installation token is usually a better fit than a user-owned PAT:
That said, I agree with your point about trusted publishing. It is great where supported, but the support matrix still has gaps, and those gaps push people back toward long-lived or manually rotated tokens. So I would not call this solved just by saying "use trusted publishing". GitHub should probably make the PAT creation page clearer when an org is hidden because of policy, and ideally show something like:
That would save a lot of guessing. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
🏷️ Discussion Type
Bug
Body
So I am trying to create an access token with organization access, but I can't seem to actually... select organizations I belong to.
As a side note, I am having to do this so I can auto-recreate tokens on the regular because trusted publishing is so limited in it's support!
Beta Was this translation helpful? Give feedback.
All reactions