jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-19 18:10:59 -05:00
Code Issues Projects Releases Wiki Activity

Part 2: Second fourth content unordered lists from dash to asterisk (#51095)

Browse Source
This commit is contained in:
Grace Park
2024-06-13 10:44:18 -07:00
committed by GitHub
parent 0b94935b77
commit 6acca22e47
385 changed files with 2873 additions and 2842 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
content/packages/managing-github-packages-using-github-actions-workflows/example-workflows-for-publishing-a-package.md
View File

@@ -12,7 +12,7 @@ shortTitle: Example workflows
You can find example workflows in "[AUTOTITLE](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions)" or in any of these {% data variables.product.prodname_actions %} guides:
- [Publishing Node.js packages](/actions/publishing-packages/publishing-nodejs-packages)
- [Publishing Docker images](/actions/publishing-packages/publishing-docker-images)
- [Publishing Java packages with Maven](/actions/publishing-packages/publishing-java-packages-with-maven)
- [Publishing Java packages with Gradle](/actions/publishing-packages/publishing-java-packages-with-gradle)
* [Publishing Node.js packages](/actions/publishing-packages/publishing-nodejs-packages)
* [Publishing Docker images](/actions/publishing-packages/publishing-docker-images)
* [Publishing Java packages with Maven](/actions/publishing-packages/publishing-java-packages-with-maven)
* [Publishing Java packages with Gradle](/actions/publishing-packages/publishing-java-packages-with-gradle)

8
content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md
View File

@@ -65,8 +65,8 @@ When you enable GitHub Actions, GitHub installs a GitHub App on your repository.
For packages in registries that support granular permissions, when you create, install, modify, or delete a package through a workflow, there are some default permission and access settings used to ensure admins have access to the workflow. You can adjust these access settings as well. For the list of registries that support granular permissions, see "[AUTOTITLE](/packages/learn-github-packages/about-permissions-for-github-packages#granular-permissions-for-userorganization-scoped-packages)."
For example, by default if a workflow creates a package using the `GITHUB_TOKEN`, then:
- The package inherits the visibility and permissions model of the repository where the workflow is run.
- Repository admins where the workflow is run become the admins of the package once the package is created.
* The package inherits the visibility and permissions model of the repository where the workflow is run.
* Repository admins where the workflow is run become the admins of the package once the package is created.
These are more examples of how default permissions work for workflows that manage packages.
@@ -99,8 +99,8 @@ Create a new workflow file in your repository (such as `.github/workflows/deploy
**Notes:**
- {% data reusables.actions.actions-not-certified-by-github %}
- {% data reusables.actions.actions-use-sha-pinning %}
* {% data reusables.actions.actions-not-certified-by-github %}
* {% data reusables.actions.actions-use-sha-pinning %}
{% endnote %}