-
Notifications
You must be signed in to change notification settings - Fork 60.6k
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
Statement implies that GITHUB_TOKEN cannot be used to install private packages #35922
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. |
@jlawrence Thank you for raising this issue! I'll get this triaged for review ✨ Our team will provide feedback regarding the best next steps for this issue - thanks for your patience! 💛 |
Thanks for opening an issue! We've triaged this issue for technical review by a subject matter expert 👀 |
This comment was marked as spam.
This comment was marked as spam.
@jlawrence Thank you so much for your patience while our SME team reviewed! They wanted to relay the following:
Would you be willing to submit a PR to update the docs to align with guidance above? 💛 |
@nguyenalex836 Thanks for the guidance. I have submitted a PR following the guidance: #36017 |
For clarity and correctness, I suggest the following change to this line:
Remove the phrase "(which GITHUB_TOKEN can't access)", and add the following sentence as a new bullet point:
"If you grant a repository read access to a private package, then that repository's workflows can use GITHUB_TOKEN to install that package (https://docs.github.com/en/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-workflow-access-to-your-package)"
The text was updated successfully, but these errors were encountered: