caaee7a124
* Add back changes from prior to purge * Manually fix some invalid Liquid * Updoot render-content * Improve test messages to show correct output * Run el scripto * Pass the remaining test
3.2 KiB
3.2 KiB
title, intro, redirect_from, versions
| title | intro | redirect_from | versions | ||||
|---|---|---|---|---|---|---|---|
| Permission levels for security advisories | The actions you can take in a security advisory depend on whether you have admin or write permissions to the security advisory. |
|
|
Permissions overview
{% data reusables.repositories.security-advisory-admin-permissions %} For more information about adding a collaborator to a security advisory, see "Adding a collaborator to a security advisory."
| Action | Write permissions | Admin permissions |
|---|---|---|
| See a draft security advisory | X | X |
| Add collaborators to the security advisory (see "Adding a collaborator to a security advisory") | X | |
| Edit and delete any comments in the security advisory | X | X |
| Create a temporary private fork in the security advisory (see "Collaborating in a temporary private fork to resolve a security vulnerability") | X | |
| Add changes to a temporary private fork in the security advisory (see "Collaborating in a temporary private fork to resolve a security vulnerability") | X | X |
| Create pull requests in a temporary private fork (see "Collaborating in a temporary private fork to resolve a security vulnerability") | X | X |
| Merge changes in the security advisory (see "Collaborating in a temporary private fork to resolve a security vulnerability") | X | |
| Add and edit metadata in the security advisory (see "Publishing a security advisory") | X | X |
| Add and remove credits for a security advisory (see "Editing a security advisory") | X | X |
| Close the draft security advisory | X | |
| Publish the security advisory (see "Publishing a security advisory") | X |