Package authentication documentation has confusing PAT wording

[syntastical]

Code of Conduct

• I have read and agree to the GitHub Docs project's 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 using GITHUB_SECRET in GitHub actions.

Additional information

No response

[welcome]

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.

[nguyenalex836]

@syntastical Thank you for opening an issue and linking it to your PR! ✨

[felicitymay]

@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?

{% data variables.product.prodname_registry %} supports authentication using a {% data variables.product.pat_v1 %}. Authentication using {% data variables.product.pat_v2_plural %} is not supported. For more information, see "[AUTOTITLE](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)."

Which should look like this:

GitHub Packages supports authentication using a personal access token (classic). Authentication using fine-grained personal access tokens is not supported. For more information, see "AUTOTITLE."

[felicitymay]

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.

[github-actions]

Thanks for opening an issue! We've triaged this issue for technical review by a subject matter expert 👀

[nguyenalex836]

@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 💛

[syntastical]

@nguyenalex836 sounds good, sorry I've been away. I'll circle back to this ASAP.

[github-actions]

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.