1
0
mirror of synced 2025-12-21 02:46:50 -05:00

Commonmark issue sweep [07SEPT2023] (#42191)

This commit is contained in:
Rachael Rose Renk
2023-09-11 16:05:28 -06:00
committed by GitHub
parent 0ab430dc73
commit 21e1515e5b
2 changed files with 2 additions and 2 deletions

View File

@@ -92,7 +92,7 @@ If you want to use Git hooks for your codespace, then you should set up hooks us
1. At the top right of the **Codespaces** tab, select {% octicon "kebab-horizontal" aria-label="Codespace repository configuration" %} and click **New with options**. 1. At the top right of the **Codespaces** tab, select {% octicon "kebab-horizontal" aria-label="Codespace repository configuration" %} and click **New with options**.
![Screenshot of the options dropdown in the "{% data variables.product.prodname_codespaces %}" tab, with the option "New with options" highlighted.](/assets/images/help/codespaces/default-machine-type.png) ![Screenshot of the options dropdown in the "{% data variables.product.prodname_codespaces %}" tab, with the option "New with options" highlighted.](/assets/images/help/codespaces/default-machine-type.png)
1. On the options page for your codespace, choose your preferred options from the dropdown menus. 1. On the options page for your codespace, choose your preferred options from the dropdown menus.

View File

@@ -1,3 +1,3 @@
1. Under "Affected products", define the ecosystem, package name, affected/patched versions, and vulnerable functions for the security vulnerability that this security advisory describes. If applicable, you can add multiple affected products to the same advisory by clicking **Add another affected product**. 1. Under "Affected products", define the ecosystem, package name, affected/patched versions, and vulnerable functions for the security vulnerability that this security advisory describes. If applicable, you can add multiple affected products to the same advisory by clicking **Add another affected product**.
For information about how to specify information on the form, including affected versions, see "[AUTOTITLE](/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/best-practices-for-writing-repository-security-advisories)." For information about how to specify information on the form, including affected versions, see "[AUTOTITLE](/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/best-practices-for-writing-repository-security-advisories)."