Skip to content
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.

Sign up for GitHub

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

Add colons in about-github-packages-and-github-actions#workflows-for-publishing-packages | issue/35774 #35791

Merged
merged 2 commits into from
Jan 6, 2025
+2 −2
Merged

Add colons in about-github-packages-and-github-actions#workflows-for-publishing-packages | issue/35774 #35791

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d766202
Add colons in about-github-packages-and-github-actions#workflows-for-…
Piyush-r-bhaskar Dec 30, 2024
0389a26
Merge branch 'main' into patch-7
nguyenalex836 Jan 6, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions data/reusables/package_registry/about-packaging-and-actions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@

Now, when reviewing a pull request, you'll be able to look at the workflow run and download the artifact that was produced.

![Screenshot of the "Artifacts" section of a workflow run. The name of the artifact generated by the run, "artifact," is highlighted with a dark orange outline.](/assets/images/help/repository/artifact-drop-down-updated.png)

Check warning on line 11 in data/reusables/package_registry/about-packaging-and-actions.md

View workflow job for this annotation

GitHub Actions / lint-content

Images alternate text should be between 40-150 characters 

Image alternate text is 158 characters long.

This will let you run the code in the pull request on your machine, which can help with debugging or testing the pull request.

Expand All @@ -16,12 +16,12 @@

In addition to uploading packaging artifacts for testing in a continuous integration workflow, you can create workflows that build your project and publish packages to a package registry.

* **Publish packages to {% data variables.product.prodname_registry %}**
* **Publish packages to {% data variables.product.prodname_registry %}:**
{% data variables.product.prodname_registry %} can act as a package hosting service for many types of packages. You can choose to share your packages with all of {% data variables.product.prodname_dotcom %}, or private packages to share with collaborators or an organization. For more information, see "[AUTOTITLE](/packages/learn-github-packages/introduction-to-github-packages)."

You may want to publish packages to {% data variables.product.prodname_registry %} on every push into the default branch. This will allow developers on your project to always be able to run and test the latest build from the default branch easily, by installing it from {% data variables.product.prodname_registry %}.

* **Publish packages to a package registry**
* **Publish packages to a package registry:**
For many projects, publishing to a package registry is performed whenever a new version of a project is released. For example, a project that produces a JAR file may upload new releases to the Maven Central repository. Or, a .NET project may produce a nuget package and upload it to the NuGet Gallery.

You can automate this by creating a workflow that publishes packages to a package registry on every release creation. For more information, see "[AUTOTITLE](/repositories/releasing-projects-on-github/managing-releases-in-a-repository)."
Loading