Skip to content

Fix category format and enhance package details #46254

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

Open
tapanrathod wants to merge 1 commit into
base: main
Choose a base branch
from
+4 −3
Open

Fix category format and enhance package details #46254

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
7 changes: 4 additions & 3 deletions content/packages/learn-github-packages/publishing-a-package.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,8 +10,7 @@
fpt: '*'
ghes: '*'
ghec: '*'
category:
- Publish and manage packages
category: Publish and manage packages

Check failure on line 13 in content/packages/learn-github-packages/publishing-a-package.md

View workflow job for this annotation

GitHub Actions / lint-content

Frontmatter must conform to the schema 

Frontmatter must be an array, which is written in frontmatter like:
---

{% data reusables.package_registry.packages-ghes-release-stage %}
Expand All @@ -20,7 +19,9 @@

You can help people understand and use your package by providing a description and other details like installation and usage instructions on the package page. {% data variables.product.github %} provides metadata for each version, such as the publication date, download activity, and recent versions. For an example package page, see [@Codertocat/hello-world-npm](https://github.com/Codertocat/hello-world-npm/packages/10696?version=1.0.1).

{% data reusables.package_registry.public-or-private-packages %} A repository can be connected to more than one package. To prevent confusion, make sure the README and description clearly provide information about each package.
{% data reusables.package_registry.public-or-private-packages %}

A repository can be connected to more than one package. To prevent confusion, make sure the README and description clearly provide information about each package.

{% ifversion fpt or ghec %}
If a new version of a package fixes a security vulnerability, you should publish a security advisory in your repository. {% data variables.product.prodname_dotcom %} reviews each published security advisory and may use it to send {% data variables.product.prodname_dependabot_alerts %} to affected repositories. For more information, see [AUTOTITLE](/code-security/concepts/vulnerability-reporting-and-management/repository-security-advisories).
Expand Down
Loading