The docs build (.github/workflows/docs.yml) restores Intility.DotnetApiDocs from the private GitHub Packages feed.
Intility.DotnetApiDocs will stay private for a while, so we can't drop the private feed dependency yet. But once this repo goes public, secrets.GITHUB_TOKEN of a public repo can no longer read private org packages by default.
Required action before flipping public
Configure GitHub Packages Actions access on the Intility.DotnetApiDocs package:
- Go to the
Intility.DotnetApiDocs package page on GitHub
- Settings → Manage Actions access
- Add
intility/json-api-toolkit with Read role
After that, GITHUB_TOKEN works from the public repo without needing a PAT.
GitHub docs reference
Long-term
When Intility.DotnetApiDocs is published to nuget.org, the source-url block in docs.yml can be dropped entirely.
Related: #143, #144
Blocks: making the repo public.
The docs build (
.github/workflows/docs.yml) restoresIntility.DotnetApiDocsfrom the private GitHub Packages feed.Intility.DotnetApiDocswill stay private for a while, so we can't drop the private feed dependency yet. But once this repo goes public,secrets.GITHUB_TOKENof a public repo can no longer read private org packages by default.Required action before flipping public
Configure GitHub Packages Actions access on the
Intility.DotnetApiDocspackage:Intility.DotnetApiDocspackage page on GitHubintility/json-api-toolkitwith Read roleAfter that,
GITHUB_TOKENworks from the public repo without needing a PAT.GitHub docs reference
Long-term
When
Intility.DotnetApiDocsis published to nuget.org, thesource-urlblock indocs.ymlcan be dropped entirely.Related: #143, #144
Blocks: making the repo public.