jprdonnelly/docs
1
0
Fork 0
mirror of synced 2026-01-28 18:03:28 -05:00
Code Issues Projects Releases Wiki Activity

Merge pull request #26832 from github/repo-sync

Browse Source 
Repo sync
This commit is contained in:
docs-bot
2023-07-17 00:59:29 -07:00
committed by GitHub
parent f46d49867e c89c580c22
commit b33d409e1e
1 changed files with 10 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
content/code-security/security-advisories/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md
View File

@@ -38,7 +38,16 @@ To keep information about vulnerabilities secure, integrations, including CI, ca
![Screenshot of the "Collaborate on a patch in private" area of the form. A button, labeled "Start a temporary private fork", is outlined in dark orange.](/assets/images/help/security/new-temporary-private-fork-button.png)
A private fork of the repository is created and shown on the advisory page.
A private fork of the repository is created and shown on the advisory page.
The naming convention for the private fork is very similar to the convention used for advisories in the {% data variables.product.prodname_advisory_database %} and follows this format: `repo-ghsa-xxxx-xxxx-xxxx`, where:
- `repo` is the name of the repository. To stay under the 100 character limit on repository names, we truncate the original repository's name to 80 characters.
- `xxxx-xxxx-xxxx` is the unique identifier of the draft security advisory:
- `x` is a letter or a number from the following set: `23456789cfghjmpqrvwx`.
- The numbers and letters are randomly assigned.
- All letters and numbers are lowercase.
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`.
## Adding collaborators to a temporary private fork