You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/packages/index.md
+15-16Lines changed: 15 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,30 +4,30 @@ shortTitle: '{% data variables.product.prodname_registry %}'
4
4
intro: 'Learn to safely publish and consume packages, store your packages alongside your code, and share your packages privately with your team or publicly with the open source community. You can also automate your packages with {% data variables.product.prodname_actions %}.'
Copy file name to clipboardExpand all lines: content/packages/learn-github-packages/connecting-a-repository-to-a-package.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,6 +10,8 @@ versions:
10
10
ghec: '*'
11
11
ghes: '*'
12
12
shortTitle: Connect a repository
13
+
category:
14
+
- Publish and manage packages
13
15
---
14
16
15
17
When you publish a package that is scoped to a personal account or an organization, the package is not linked to a repository by default. If you connect a package to a repository, the package's landing page will show information and links from the repository, such as the README. You can also choose to have the package inherit its access permissions from the linked repository. For more information, see [AUTOTITLE](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility).
Copy file name to clipboardExpand all lines: content/packages/managing-github-packages-using-github-actions-workflows/about-github-packages-and-github-actions.md
0 commit comments