Skip to content

Commit 306001b

Browse files
[EDI] Adding a collaborator to a repository security advisory (#59796)
1 parent c928e1f commit 306001b

2 files changed

Lines changed: 4 additions & 9 deletions

File tree

content/code-security/how-tos/report-and-fix-vulnerabilities/fix-reported-vulnerabilities/adding-a-collaborator-to-a-repository-security-advisory.md

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Adding a collaborator to a repository security advisory
3-
intro: You can add other users or teams to collaborate on a security advisory with you.
3+
intro: Add other users or teams to collaborate on a security advisory with you.
44
permissions: '{% data reusables.permissions.security-repo-enable %}'
55
redirect_from:
66
- /articles/adding-a-collaborator-to-a-maintainer-security-advisory
@@ -21,9 +21,7 @@ topics:
2121
shortTitle: Add collaborators
2222
---
2323

24-
{% data reusables.security-advisory.repository-level-advisory-note %}
25-
26-
## Adding a collaborator to a security advisory
24+
This article applies to repository-level security advisories in a public repository. To edit a global advisory in the {% data variables.product.prodname_advisory_database %}, see [AUTOTITLE](/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/editing-security-advisories-in-the-github-advisory-database).
2725

2826
Collaborators have write permissions to the security advisory. For more information, see [AUTOTITLE](/code-security/security-advisories/working-with-repository-security-advisories/permission-levels-for-repository-security-advisories).
2927

@@ -40,6 +38,4 @@ Collaborators have write permissions to the security advisory. For more informat
4038

4139
## Further reading
4240

43-
* [AUTOTITLE](/code-security/security-advisories/working-with-repository-security-advisories/permission-levels-for-repository-security-advisories)
4441
* [AUTOTITLE](/code-security/security-advisories/working-with-repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)
45-
* [AUTOTITLE](/code-security/security-advisories/working-with-repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory).
Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,3 @@
11
> [!NOTE]
2-
> This article applies to editing repository-level advisories as an owner of a public repository.
3-
>
4-
> Users who are not repository owners can contribute to global security advisories in the {% data variables.product.prodname_advisory_database %} at [github.com/advisories](https://github.com/advisories). Edits to global advisories will not change or affect how the advisory appears on the repository. For more information, see [AUTOTITLE](/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/editing-security-advisories-in-the-github-advisory-database).
2+
> This article applies to repository-level security advisories in a public repository.
3+
> To edit a global advisory in the {% data variables.product.prodname_advisory_database %}, see [AUTOTITLE](/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/editing-security-advisories-in-the-github-advisory-database).

0 commit comments

Comments
 (0)