update data reusables
This commit is contained in:
Rachael Sewell
@@ -1,6 +1,6 @@
|
||||
1. Right-click the commit.
|
||||
|
||||
- If a commit has only one tag, click **Delete Tag TAG NAME**.
|
||||
|
||||
- If a commit has multiple tags, hover over **Delete Tag...** and then click the tag that you want to delete.
|
||||
|
||||
- If a commit has only one tag, click **Delete Tag TAG NAME**.
|
||||
|
||||
- If a commit has multiple tags, hover over **Delete Tag...** and then click the tag that you want to delete.
|
||||
|
||||
|
||||
@@ -1,2 +1,3 @@
|
||||
1. In the menu bar, select **{% data variables.product.prodname_desktop %}**, then click **Preferences**.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,2 +1,3 @@
|
||||
1. Optionally, next to "Usage this month", click **Get usage report** to email a CSV report of storage use for {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %} to the account's primary email address.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,2 +1,3 @@
|
||||
1. Under "Current plan", next to the name of your plan, select **Edit** and click **Add seats**.
|
||||
|
||||
|
||||
|
||||
@@ -1,2 +1,3 @@
|
||||
1. Next to the pending change you'd like to cancel, click **Cancel**.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,2 +1,3 @@
|
||||
1. Next to "{% data variables.large_files.product_name_short %} Data", click **Add more data** or use the **Edit** drop-down and click **Add more data packs**.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,2 +1,3 @@
|
||||
1. Optionally, under the billing summary at the top of the page click **Get usage report** to email a CSV report of storage use for {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, and {% data variables.product.prodname_github_codespaces %} in each of your enterprise account's organizations to the primary email address for the account.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,2 +1,3 @@
|
||||
1. In the left sidebar, under the list of repositories, use the "Manage notifications" drop-down to click **Notification settings**.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,2 +1,3 @@
|
||||
1. Optionally, filter the list of alerts. You can click multiple filters in the drop-down filter menus to narrow your search. You can also type search qualifiers in the **Search repositories** field. For more information about the available qualifiers, see "[AUTOTITLE](/code-security/security-overview/filtering-alerts-in-security-overview)."
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,26 +1,26 @@
|
||||
{% data reusables.package_registry.packages-classic-pat-only %}
|
||||
|
||||
1. Create a new {% data variables.product.pat_v1 %} with the appropriate scopes for the tasks you want to accomplish. If your organization requires SSO, you must enable SSO for your new token.
|
||||
{% warning %}
|
||||
{% warning %}
|
||||
|
||||
**Note:** By default, when you select the `write:packages` scope for your {% data variables.product.pat_v1 %} in the user interface, the `repo` scope will also be selected. The `repo` scope offers unnecessary and broad access, which we recommend you avoid using for {% data variables.product.prodname_actions %} workflows in particular. For more information, see "[AUTOTITLE](/actions/security-guides/security-hardening-for-github-actions#considering-cross-repository-access)." As a workaround, you can select just the `write:packages` scope for your {% data variables.product.pat_v1 %} in the user interface with this url: `https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/settings/tokens/new?scopes=write:packages`.
|
||||
**Note:** By default, when you select the `write:packages` scope for your {% data variables.product.pat_v1 %} in the user interface, the `repo` scope will also be selected. The `repo` scope offers unnecessary and broad access, which we recommend you avoid using for {% data variables.product.prodname_actions %} workflows in particular. For more information, see "[AUTOTITLE](/actions/security-guides/security-hardening-for-github-actions#considering-cross-repository-access)." As a workaround, you can select just the `write:packages` scope for your {% data variables.product.pat_v1 %} in the user interface with this url: `https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/settings/tokens/new?scopes=write:packages`.
|
||||
|
||||
{% endwarning %}
|
||||
{% endwarning %}
|
||||
|
||||
- Select the `read:packages` scope to download container images and read their metadata.
|
||||
- Select the `write:packages` scope to download and upload container images and read and write their metadata.
|
||||
- Select the `delete:packages` scope to delete container images.
|
||||
- Select the `read:packages` scope to download container images and read their metadata.
|
||||
- Select the `write:packages` scope to download and upload container images and read and write their metadata.
|
||||
- Select the `delete:packages` scope to delete container images.
|
||||
|
||||
For more information, see "[AUTOTITLE](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)."
|
||||
For more information, see "[AUTOTITLE](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)."
|
||||
|
||||
2. Save your {% data variables.product.pat_v1 %}. We recommend saving your token as an environment variable.
|
||||
```shell
|
||||
$ export CR_PAT=YOUR_TOKEN
|
||||
```
|
||||
```shell
|
||||
$ export CR_PAT=YOUR_TOKEN
|
||||
```
|
||||
3. Using the CLI for your container type, sign in to the {% data variables.product.prodname_container_registry %} service at `{% data reusables.package_registry.container-registry-hostname %}`.
|
||||
{% raw %}
|
||||
```shell
|
||||
$ echo $CR_PAT | docker login {% endraw %}{% data reusables.package_registry.container-registry-hostname %}{% raw %} -u USERNAME --password-stdin
|
||||
> Login Succeeded
|
||||
```
|
||||
{% endraw %}
|
||||
{% raw %}
|
||||
```shell
|
||||
$ echo $CR_PAT | docker login {% endraw %}{% data reusables.package_registry.container-registry-hostname %}{% raw %} -u USERNAME --password-stdin
|
||||
> Login Succeeded
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
@@ -1,3 +1,4 @@
|
||||
1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of your organization.
|
||||
2. Under your organization name, click the {% octicon "package" aria-hidden="true" %} **Packages** tab.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,3 +1,4 @@
|
||||
1. Search for and then click the name of the package that you want to manage.
|
||||
4. On your package's landing page, on the right-hand side, click **{% octicon "gear" aria-hidden="true" %} Package settings**.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,2 +1,3 @@
|
||||
1. At the top right corner of the list of package versions, use the **Select versions view** dropdown and select **Deleted**.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,2 +1,3 @@
|
||||
1. In the right sidebar of your repository, click **Packages**.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,4 +1,5 @@
|
||||
1. After confirming that your DNS configuration has updated, you can verify the domain. If the change wasn't immediate, and you have navigated away from the previous page, return to your Pages settings by following the first few steps and, to the right of the domain, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} and then click **Continue verifying**.
|
||||
|
||||
|
||||
|
||||
1. To verify your domain, click **Verify**.
|
||||
2. To make sure your custom domain remains verified, keep the TXT record in your domain's DNS configuration.
|
||||
|
||||
@@ -1,2 +1,3 @@
|
||||
1. In the upper-right corner of the notes, click {% octicon "kebab-horizontal" aria-label="Card menu" %}.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,2 +1,3 @@
|
||||
1. Place your cursor in the bottom row of the project, next to the {% octicon "plus" aria-label="Create new item or add existing item" %}.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,4 +1,5 @@
|
||||
1. Optionally, to change the repository, click the dropdown and select a repository. You can also search for specific issues and pull requests.
|
||||
|
||||
|
||||
|
||||
1. Select the issues and pull requests you want to add.
|
||||
1. Click **Add selected items**.
|
||||
|
||||
@@ -1,11 +1,12 @@
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.user-settings.access_org %}
|
||||
1. Under your organization name, click {% octicon "table" aria-hidden="true" %} **Projects**.
|
||||
|
||||
|
||||
|
||||
1. Click **New project**.
|
||||
1. Optionally, in the text box under "Project name", type a name for your new project.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Click a {% ifversion projects-v2-org-templates %}built-in template, a template from your organization{% else %}template{% endif %} or, to start with an empty project, click **Table** or **Board**.
|
||||
1. Click **Create**.
|
||||
|
||||
@@ -1,2 +1,3 @@
|
||||
1. Click {% octicon "triangle-down" aria-label="View options" %} next to the name of the currently open view.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,2 +1,3 @@
|
||||
1. Under your repository name, click {% octicon "play" aria-hidden="true" %} **Actions**.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
1. Above the list of files, click {% octicon "code" aria-hidden="true" %} **Code**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Copy the URL for the repository.
|
||||
|
||||
@@ -7,4 +8,4 @@
|
||||
- To clone the repository using an SSH key, including a certificate issued by your organization's SSH certificate authority, click **SSH**, then click {% octicon "clippy" aria-label="Copy to clipboard" %}.
|
||||
- To clone a repository using {% data variables.product.prodname_cli %}, click **{% data variables.product.prodname_cli %}**, then click {% octicon "copy" aria-label="Copy to clipboard" %}.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,10 +1,11 @@
|
||||
2. At the top of the comment, click **edited** to open the edit history.
|
||||
|
||||
{% note %}
|
||||
{% note %}
|
||||
|
||||
**Note:** If you don't see the **edited** option, then the comment doesn't have an edit history.
|
||||
**Note:** If you don't see the **edited** option, then the comment doesn't have an edit history.
|
||||
|
||||
{% endnote %}
|
||||
{% endnote %}
|
||||
|
||||
3. To view the details of a specific change, select it from the list of edits.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
1. Above the list of files, click {% octicon "code" aria-hidden="true" %} **Code**.
|
||||
|
||||
|
||||
|
||||
1. To clone and open the repository with {% data variables.product.prodname_desktop %}, click {% octicon "desktop-download" aria-hidden="true" %} **Open with {% data variables.product.prodname_desktop %}**.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -2,22 +2,22 @@
|
||||
{% data reusables.repositories.sidebar-security %}
|
||||
1. Click **Report a vulnerability** to open the advisory form.
|
||||
1. Fill in the advisory details form.
|
||||
{% tip %}
|
||||
{% tip %}
|
||||
|
||||
**Tip:** In this form, only the title and description are mandatory. (In the general draft security advisory form, which the repository maintainer initiates, specifying the ecosystem is also required.) However, we recommend security researchers provide as much information as possible on the form so that the maintainers can make an informed decision about the submitted report. You can adopt the template used by our security researchers from the {% data variables.product.prodname_security %}, which is available on the [`github/securitylab` repository](https://github.com/github/securitylab/blob/main/docs/report-template.md)."
|
||||
**Tip:** In this form, only the title and description are mandatory. (In the general draft security advisory form, which the repository maintainer initiates, specifying the ecosystem is also required.) However, we recommend security researchers provide as much information as possible on the form so that the maintainers can make an informed decision about the submitted report. You can adopt the template used by our security researchers from the {% data variables.product.prodname_security %}, which is available on the [`github/securitylab` repository](https://github.com/github/securitylab/blob/main/docs/report-template.md)."
|
||||
|
||||
{% endtip %}
|
||||
{% endtip %}
|
||||
|
||||
For more information about the fields available and guidance on filling in the form, see "[AUTOTITLE](/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory)" and "[AUTOTITLE](/code-security/security-advisories/guidance-on-reporting-and-writing/best-practices-for-writing-repository-security-advisories)."
|
||||
For more information about the fields available and guidance on filling in the form, see "[AUTOTITLE](/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory)" and "[AUTOTITLE](/code-security/security-advisories/guidance-on-reporting-and-writing/best-practices-for-writing-repository-security-advisories)."
|
||||
|
||||
1. At the bottom of the form, click **Submit report**. {% data variables.product.prodname_dotcom %} will display a message letting you know that maintainers have been notified and that you have a pending credit for this security advisory.
|
||||
|
||||
{% tip %}
|
||||
{% tip %}
|
||||
|
||||
**Tip:** When the report is submitted, {% data variables.product.prodname_dotcom %} automatically adds the reporter of the vulnerability as a collaborator and as a credited user on the proposed advisory.
|
||||
**Tip:** When the report is submitted, {% data variables.product.prodname_dotcom %} automatically adds the reporter of the vulnerability as a collaborator and as a credited user on the proposed advisory.
|
||||
|
||||
{% endtip %}
|
||||
{% endtip %}
|
||||
|
||||
1. Optionally, click **Start a temporary private fork** if you want to start to fix the issue. Note that only the repository maintainer can merge changes from that private fork into the parent repository.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,2 +1,3 @@
|
||||
1. In the upper-right corner of any page, click your profile photo, then click ** Your stars**.
|
||||
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user