Skip to content

Commit f86c9ed

Browse files
authored
Merge pull request #30202 from github/repo-sync
Repo sync
2 parents ce95284 + d3f2b20 commit f86c9ed

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

content/code-security/security-advisories/working-with-repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -50,6 +50,8 @@ To keep information about vulnerabilities secure, integrations, including CI, ca
5050

5151
For example, if you create a temporary private fork in a repository called `octocat-repo`, and the automatically generated ID for the draft advisory is `GHSA-x854-cvjg-vx26`, the temporary fork will be called `octocat-repo-ghsa-x854-cvjg-vx26`.
5252

53+
You can also use the REST API to create temporary private forks. For more information, see "[Create a temporary private fork](/rest/security-advisories/repository-advisories#create-a-temporary-private-fork)" in the REST API documentation.
54+
5355
## Adding collaborators to a temporary private fork
5456

5557
Anyone with admin permissions to a security advisory can add additional collaborators to the security advisory, and collaborators on the security advisory can access the temporary private fork. For more information, see "[AUTOTITLE](/code-security/security-advisories/working-with-repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)."

0 commit comments

Comments
 (0)