* Update README * [Universe] Dark mode (#16545) * Dark mode updates (#16696) * [Universe] Corporate sponsors (#16457) * Dependency review beta (#16563) * Add placeholder topic file * Revert change I didn't make I'm not sure where this change came from or why it's showing up in my PR here but I didn't make this change and it's not part of Dependency Review so I'm reverting it. * Un-revert previous change OK I see what happened there. I was comparing the PR to main rather than the Universe megabranch, hence it showed a change I didn't make. This commit undoes the change I do not want to revert on the megabranch. * Update image to add the Checks tab * Finish updating topic to mention DR * Fix check errors * Fix another versioning error * Add a sentence about supported ecosystems * Add review changes * Remove Further reading topics in same category As suggested by James, I've removed the links to topics that are in the same `/collaborating-with-issues-and-pull-requests/` category as this topic. * Update content/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies.md Co-authored-by: James Fletcher <42464962+jf205@users.noreply.github.com> * Update content/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies.md Co-authored-by: James Fletcher <42464962+jf205@users.noreply.github.com> * Update content/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies.md Co-authored-by: James Fletcher <42464962+jf205@users.noreply.github.com> * Update content/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies.md * Updates in the light of Maya's review * Remove use of "exploit" in description * Change 'dependency review summary' to 'dependency review' See PR review comment from Maya. * Mention that the age of the dependency is given * Update screenshots to latest GUI * Add details of dependency ordering within a DR * Update content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md Co-authored-by: James Fletcher <42464962+jf205@users.noreply.github.com> * Update content/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies.md Co-authored-by: James Fletcher <42464962+jf205@users.noreply.github.com> * Update content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md Co-authored-by: James Fletcher <42464962+jf205@users.noreply.github.com> Co-authored-by: James Fletcher <42464962+jf205@users.noreply.github.com> * [Universe 2020] New audit log REST API endpoint (#16699) * Minimal updates for preview * ✨ API previews ✨ * Update beta note * ✨ Update API previews ✨ * ✨ Update previews ✨ * Add draft section for git events * Clean API previews * More fixes + API previews * Address review comments + update API previews * Mention cursor-based pagination * Update content/rest/overview/resources-in-the-rest-api.md Co-authored-by: Jeff Saracco <jeffsaracco@github.com> * Temporarily revert API previews * Small tweaks from review comments + API previews * revert json schemas * Updating OpenAPI descriptions (#16776) * Updating OpenAPI descriptions * Add decorated OpenAPI schema files Co-authored-by: Jeff Saracco <jeffsaracco@github.com> Co-authored-by: skedwards88 <skedwards88@github.com> Co-authored-by: github-openapi-bot <69533958+github-openapi-bot@users.noreply.github.com> * [Universe 2020] GitHub Actions: Workflow visualization (#16629) * initial empty commit * replace image used only for dotcom * add new image and version usage * add new image and version usage * add new image and version usage * add new image and version usage, delete unneeded image * add new image and version usage, fix incorrect image * add new image and version usage * add new image and version usage * add new image and version usage * add new image and version usage * update screenshot update * add new image and version usage * add new image and version usage * update text * update images and fix list numbering * add step with graph * Add missing versioning * add overview of visualization * fix title to match filename * add beta note * update wording * Restructuring packages (#16731) * restructuring packages * moving more content * moving more content * fixing the toc for guides * removing CR from the landing page * adjusting qs * updating npm * enhancing guides * Update updating-github-insights.md * fixing link problems * fixing link problems * redirecting the redirects * another change * fixing the guides landing page * add packages quickstart * moving CR content * adding some descriptive text * add packages landing page * adding guide content back * update popular articles based on data * fix caps on product name * try removing product from front matter * Update content/packages/quickstart.md Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com> * Update content/packages/quickstart.md Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com> * add node package instructions to quickstart * fixing links and adding redirect * fixing redirects * renaming to container guides * renaming to container guides and fixing reusables * adding context and about section to CR * removign landign page extra titles and descriptions * reverting the packages * updating link * Apply suggestions from code review Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com> * Apply suggestions from code review Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com> * updating * update test to reflect redesigned product landing page * Add private vs public clarification * Fix borked test * filter out standalone category files from test Co-authored-by: Cynthia Rich <crichID@github.com> Co-authored-by: Cynthia Rich <crichID@users.noreply.github.com> Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com> Co-authored-by: Sarah Schneider <sarahs@github.com> Co-authored-by: Jason Etcovitch <jasonetco@github.com> * Add discussions video See https://github.com/github/docs-internal/pull/16759 * Remove typos * update article name in test Co-authored-by: Laura Coursen <lecoursen@github.com> Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com> Co-authored-by: hubwriter <hubwriter@github.com> Co-authored-by: James Fletcher <42464962+jf205@users.noreply.github.com> Co-authored-by: Shati Patel <42641846+shati-patel@users.noreply.github.com> Co-authored-by: Jeff Saracco <jeffsaracco@github.com> Co-authored-by: skedwards88 <skedwards88@github.com> Co-authored-by: github-openapi-bot <69533958+github-openapi-bot@users.noreply.github.com> Co-authored-by: Meg Bird <megbird@github.com> Co-authored-by: Leona B. Campbell <3880403+runleonarun@users.noreply.github.com> Co-authored-by: Cynthia Rich <crichID@github.com> Co-authored-by: Cynthia Rich <crichID@users.noreply.github.com> Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com> Co-authored-by: Sarah Schneider <sarahs@github.com> Co-authored-by: Jason Etcovitch <jasonetco@github.com>
4.7 KiB
title, intro, product, redirect_from, versions
| title | intro | product | redirect_from | versions | ||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Using GitHub Packages with GitHub Actions | You can configure a workflow in {% data variables.product.prodname_actions %} to automatically publish or install a package from {% data variables.product.prodname_registry %}. | {% data reusables.gated-features.packages %} |
|
|
{% data reusables.package_registry.packages-ghes-release-stage %}
About {% data variables.product.prodname_registry %} with {% data variables.product.prodname_actions %}
{% data reusables.repositories.about-github-actions %} {% data reusables.repositories.actions-ci-cd %} For more information, see "About {% data variables.product.prodname_actions %}."
You can extend the CI and CD capabilities of your repository by publishing or installing packages as part of your workflow.
{% if currentVersion == "free-pro-team@latest" %}
Authenticating to {% data variables.product.prodname_github_container_registry %}
{% data reusables.package_registry.container-registry-beta %}
{% data reusables.package_registry.authenticate_with_pat_for_container_registry %}
For an authentication example, see "Authenticating with the {% data variables.product.prodname_container_registry %}."
{% endif %}
Authenticating to package registries on {% data variables.product.prodname_dotcom %}
{% if currentVersion == "free-pro-team@latest" %}If you want your workflow to authenticate to {% data variables.product.prodname_registry %} to access a package registry other than the {% data variables.product.prodname_container_registry %} on {% data variables.product.product_name %}, then{% else %}To authenticate to package registries on {% data variables.product.product_name %},{% endif %} we recommend using the GITHUB_TOKEN that {% data variables.product.product_name %} automatically creates for your repository when you enable {% data variables.product.prodname_actions %} instead of a personal access token for authentication. The GITHUB_TOKEN has read:packages and write:packages scopes to the current repository. For forks, the token also has the read:packages scope for the parent repository.
You can reference the GITHUB_TOKEN in your workflow file using the {% raw %}{{secrets.GITHUB_TOKEN}}{% endraw %} context. For more information, see "Authenticating with the GITHUB_TOKEN."
Publishing a package using an action
You can publish packages as part of your continuous integration (CI) flow using {% data variables.product.prodname_actions %}. For example, you could configure a workflow so that anytime a developer pushes code to the default branch, the workflow runs CI tests. If those tests pass, the workflow publishes a new package version to {% data variables.product.prodname_registry %}. This workflow automates the creation of new package versions only if the code meets your quality standards.
{% data reusables.package_registry.actions-configuration %}
Installing a package using an action
You can install packages as part of your CI flow using {% data variables.product.prodname_actions %}. For example, you could configure a workflow so that anytime a developer pushes code to a pull request, the workflow resolves dependencies by downloading and installing packages hosted by {% data variables.product.prodname_registry %}. Then, the workflow can run CI tests that require the dependencies.
Installing packages hosted by {% data variables.product.prodname_registry %} through {% data variables.product.prodname_actions %} requires minimal configuration or additional authentication when you use GITHUB_TOKEN.{% if currentVersion == "free-pro-team@latest" %} Data transfer is also free when an action installs a package. For more information, see "About billing for {% data variables.product.prodname_registry %}."{% endif %}
{% if currentVersion == "free-pro-team@latest" %}
GITHUB_TOKEN cannot install packages from any private repository besides the repository where the action runs. You cannot currently use GITHUB_TOKEN to authenticate to {% data variables.product.prodname_github_container_registry %}.
{% endif %}
{% data reusables.package_registry.actions-configuration %}