-
Notifications
You must be signed in to change notification settings - Fork 59.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Package authentication documentation has confusing PAT wording #33925
Comments
Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines. |
@syntastical Thank you for opening an issue and linking it to your PR! ✨ |
@syntastical - thanks for raising this issue. It's always good to know when documentation is confusing. The note that you find confusing is intended to explain that classic PAT can be used to access the package registry, but that fine-grained PATs are not supported. For information about the two types of tokens see: Managing your personal access tokens - GitHub Docs. I think that the best solution here would be to update the text of the file that contains the note, rather than to delete the reference to the note: https://github.com/github/docs/blob/main/data/reusables/package_registry/packages-classic-pat-only.md?plain=1 I suggest that this amendment would be clearer. What do you think?
Which should look like this:
|
Someone else has raised an issue about this subject too and it's left me wondering what the accurate answer is here. I'm going to tag this for review by a subject matter expert. |
Thanks for opening an issue! We've triaged this issue for technical review by a subject matter expert 👀 |
@syntastical Hello! 👋 We received confirmation from an SME that GitHub Packages supports the legacy PAT and GITHUB_TOKEN, but no fine-grained access tokens. Once you have updated your PR with the guidance @felicitymay provided above, we will be happy to get your PR merged 💛 |
@nguyenalex836 sounds good, sorry I've been away. I'll circle back to this ASAP. |
This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further. See this blog post on bug reports and the importance of repro steps for more information about the kind of information that may be helpful. |
Code of Conduct
What article on docs.github.com is affected?
https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-container-registry#authenticating-to-the-container-registry
https://docs.github.com/en/packages/learn-github-packages/publishing-a-package
What changes are you suggesting?
Remove the reusable section that states
GitHub Packages only supports authentication using a personal access token (classic). For more information, see "[Managing your personal access tokens](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)."
. But this isn't true, and is directly contradicted by references to usingGITHUB_SECRET
in GitHub actions.Additional information
No response
The text was updated successfully, but these errors were encountered: