Merge branch 'main' into plural-scopes-allowed
This commit is contained in:
Courtney Wilson
Binary file not shown.
|
Before Width: | Height: | Size: 19 KiB After Width: | Height: | Size: 66 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 5.8 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 6.8 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 4.2 KiB After Width: | Height: | Size: 33 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 128 KiB After Width: | Height: | Size: 168 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 15 KiB After Width: | Height: | Size: 50 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 57 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 14 KiB After Width: | Height: | Size: 7.1 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 22 KiB After Width: | Height: | Size: 60 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 4.8 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 13 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 5.1 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 18 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 14 KiB After Width: | Height: | Size: 7.4 KiB |
@@ -61,7 +61,7 @@ You can search the database, and use qualifiers to narrow your search. For examp
|
||||
{% endif %}| `type:unreviewed`| [**type:unreviewed**](https://github.com/advisories?query=type%3Aunreviewed) will show unreviewed advisories. |
|
||||
| `GHSA-ID`| [**GHSA-49wp-qq6x-g2rf**](https://github.com/advisories?query=GHSA-49wp-qq6x-g2rf) will show the advisory with this {% data variables.product.prodname_advisory_database %} ID. |
|
||||
| `CVE-ID`| [**CVE-2020-28482**](https://github.com/advisories?query=CVE-2020-28482) will show the advisory with this CVE ID number. |
|
||||
| `ecosystem:ECOSYSTEM`| [**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) will show only advisories affecting NPM packages. |
|
||||
| `ecosystem:ECOSYSTEM`| [**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) will show only advisories affecting npm packages. |
|
||||
| `severity:LEVEL`| [**severity:high**](https://github.com/advisories?utf8=%E2%9C%93&query=severity%3Ahigh) will show only advisories with a high severity level. |
|
||||
| `affects:LIBRARY`| [**affects:lodash**](https://github.com/advisories?utf8=%E2%9C%93&query=affects%3Alodash) will show only advisories affecting the lodash library. |
|
||||
| `cwe:ID`| [**cwe:352**](https://github.com/advisories?query=cwe%3A352) will show only advisories with this CWE number. |
|
||||
|
||||
@@ -8,6 +8,10 @@ redirect_from:
|
||||
- /github/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-a-jetbrains-ide
|
||||
- /github/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-neovim
|
||||
- /github/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio
|
||||
- /copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio-code
|
||||
- /copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-a-jetbrains-ide
|
||||
- /copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-neovim
|
||||
- /copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio
|
||||
versions:
|
||||
feature: copilot
|
||||
topics:
|
||||
|
||||
@@ -36,9 +36,9 @@ Starring a repository is a simple two-step process.
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
1. In the top-right corner of the page, click **Star**.
|
||||
|
||||
1. Optionally, to unstar a previously starred repository, click **Unstar**.
|
||||
|
||||
|
||||
1. Optionally, to unstar a previously starred repository, click **Starred**. This will remove the repository from your starred list.
|
||||
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
@@ -61,38 +61,34 @@ To view everyone who has starred a repository, add `/stargazers` to the end of t
|
||||
|
||||
Curate repositories that you've starred with public lists. You can create public lists that appear on your stars page at `https://github.com/USERNAME?tab=stars`.
|
||||
|
||||
If you add a private repository to a list, then the private repository will only appear in your list for people with `read` access to the repository.
|
||||
|
||||
|
||||
|
||||
If you add a private repository to a list, then the private repository will only appear in your list for people with `read` access to the repository.
|
||||
|
||||
You can add a repository to an existing or new list wherever you see a repository's **Star** or **Starred** dropdown menu, whether on a repository page or in a list of starred repositories.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Creating a list
|
||||
|
||||
{% data reusables.stars.stars-page-navigation %}
|
||||
2. Next to "Lists", click **Create list**.
|
||||
|
||||
3. Enter a name and description for your list and click **Create**.
|
||||
|
||||
|
||||
### Adding a repository to a list
|
||||
|
||||
{% data reusables.stars.stars-page-navigation %}
|
||||
2. Find the repository you want to add to your list.
|
||||
|
||||
2. Find the repository you want to add to your list by typing it into the search bar.
|
||||
3. Next to the repository you want to add, use the **Starred** dropdown menu and select your list.
|
||||
|
||||
|
||||
|
||||
### Removing a repository from your list
|
||||
|
||||
{% data reusables.stars.stars-page-navigation %}
|
||||
2. Select your list.
|
||||
3. Next to the repository you want to remove, use the **Starred** dropdown menu and deselect your list.
|
||||
|
||||
3. Next to the repository you want to remove, use the **Starred** drop-down menu and deselect your list.
|
||||
|
||||
|
||||
### Editing a list name or description
|
||||
|
||||
@@ -100,14 +96,14 @@ You can add a repository to an existing or new list wherever you see a repositor
|
||||
1. Select the list you want to edit.
|
||||
2. Click **Edit list**.
|
||||
3. Update the name or description and click **Save list**.
|
||||
|
||||
|
||||
|
||||
### Deleting a list
|
||||
|
||||
{% data reusables.stars.stars-page-navigation %}
|
||||
2. Select the list you want to delete.
|
||||
3. Click **Delete list**.
|
||||
|
||||
|
||||
4. To confirm, click **Delete**.
|
||||
|
||||
{% endif %}
|
||||
@@ -116,9 +112,8 @@ You can add a repository to an existing or new list wherever you see a repositor
|
||||
|
||||
You can use the search bar on your {% data variables.explore.your_stars_page %} to quickly find repositories and topics you've starred.
|
||||
|
||||
1. Go to your {% data variables.explore.your_stars_page %}.
|
||||
{% data reusables.stars.stars-page-navigation %}
|
||||
1. Use the search bar to find your starred repositories or topics by their name.
|
||||
|
||||
|
||||
The search bar only searches based on the name of a repository or topic, and not on any other qualifiers (such as the size of the repository or when it was last updated).
|
||||
|
||||
@@ -126,13 +121,11 @@ The search bar only searches based on the name of a repository or topic, and not
|
||||
|
||||
You can use sorting or filtering to customize how you see starred repositories and topics on your stars page.
|
||||
|
||||
1. Go to your {% data variables.explore.your_stars_page %}.
|
||||
1. To sort stars, select the **Sort** drop-down menu, then select **Recently starred**, **Recently active**, or **Most stars**.
|
||||
|
||||
1. To filter your list of stars based on their language, click on the desired language under **Filter by languages**.
|
||||
|
||||
1. To filter your list of stars based on repository or topic, click on the desired option.
|
||||
|
||||
{% data reusables.stars.stars-page-navigation %}
|
||||
1. To sort stars, select the **Sort by:** dropdown menu, then select **Recently starred**, **Recently active**, or **Most stars**.
|
||||
1. To filter your list of stars based on their language, click on the desired language under the **Language** dropdown menu.
|
||||
1. To filter your list of stars based on repository type, click on the desired option under the **Type:** dropdown menu.
|
||||
|
||||
|
||||
## Further reading
|
||||
|
||||
|
||||
@@ -240,7 +240,7 @@ run-npm-build:
|
||||
|
||||
</td>
|
||||
<td>
|
||||
This job installs NPM and uses it to build the app.
|
||||
This job installs npm and uses it to build the app.
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
||||
@@ -85,8 +85,8 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor
|
||||
env:
|
||||
NODE_AUTH_TOKEN: ${% raw %}{{secrets.GITHUB_TOKEN}}{% endraw %}
|
||||
```
|
||||
8. Tell NPM which scope and registry to publish packages to using one of the following methods:
|
||||
- Add an NPM configuration file for the repository by creating a `.npmrc` file in the root directory with the contents:
|
||||
8. Tell npm which scope and registry to publish packages to using one of the following methods:
|
||||
- Add an npm configuration file for the repository by creating a `.npmrc` file in the root directory with the contents:
|
||||
{% raw %}
|
||||
```shell
|
||||
@YOUR-USERNAME:registry=https://npm.pkg.github.com
|
||||
|
||||
@@ -237,7 +237,7 @@ If your instance has subdomain isolation disabled:
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghes %}
|
||||
## Using the official NPM registry
|
||||
## Using the official npm registry
|
||||
|
||||
{% data variables.product.prodname_registry %} allows you to access the official NPM registry at `registry.npmjs.com`, if your {% data variables.product.prodname_ghe_server %} administrator has enabled this feature. For more information, see [Connecting to the official NPM registry](/admin/packages/configuring-package-ecosystem-support-for-your-enterprise#connecting-to-the-official-npm-registry).
|
||||
{% data variables.product.prodname_registry %} allows you to access the official npm registry at `registry.npmjs.com`, if your {% data variables.product.prodname_ghe_server %} administrator has enabled this feature. For more information, see [Connecting to the official npm registry](/admin/packages/configuring-package-ecosystem-support-for-your-enterprise#connecting-to-the-official-npm-registry).
|
||||
{% endif %}
|
||||
|
||||
@@ -62,7 +62,16 @@ Query | Example
|
||||
<code><em>YYYY</em>-<em>MM</em>-<em>DD</em>T<em>HH</em>:<em>MM</em>:<em>SS</em>+<em>00</em>:<em>00</em></code> | **[cats created:2017-01-01T01:00:00+07:00..2017-03-01T15:30:15+07:00](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2017-01-01T01%3A00%3A00%2B07%3A00..2017-03-01T15%3A30%3A15%2B07%3A00&type=Issues)** matches issues created between January 1, 2017 at 1 a.m. with a UTC offset of `07:00` and March 1, 2017 at 3 p.m. with a UTC offset of `07:00`.
|
||||
<code><em>YYYY</em>-<em>MM</em>-<em>DD</em>T<em>HH</em>:<em>MM</em>:<em>SS</em>Z</code> | **[cats created:2016-03-21T14:11:00Z..2016-04-07T20:45:00Z](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2016-03-21T14%3A11%3A00Z..2016-04-07T20%3A45%3A00Z&type=Issues)** matches issues created between March 21, 2016 at 2:11pm and April 7, 2016 at 8:45pm.
|
||||
|
||||
## Exclude certain results
|
||||
## Exclude results that match a qualifier
|
||||
|
||||
You can narrow down search results by excluding one or more subsets. To exclude all results that are matched by a qualifier, prefix the search qualifier with a hyphen (`-`).
|
||||
|
||||
Query | Example
|
||||
------------- | -------------
|
||||
<code>-<em>QUALIFIER</em></code> | **[`cats stars:>10 -language:javascript`](https://github.com/search?q=cats+stars%3A>10+-language%3Ajavascript&type=Repositories)** matches repositories with the word "cats" that have more than 10 stars but are not written in JavaScript.
|
||||
<code>-<em>QUALIFIER</em></code> | **[`mentions:defunkt -org:github`](https://github.com/search?utf8=%E2%9C%93&q=mentions%3Adefunkt+-org%3Agithub&type=Issues)** matches issues mentioning @defunkt that are not in repositories in the GitHub organization.
|
||||
|
||||
## Exclude results with specific keywords
|
||||
|
||||
You can exclude results containing a certain word, using the `NOT` syntax. The `NOT` operator can only be used for string keywords. It does not work for numerals or dates.
|
||||
|
||||
@@ -70,13 +79,6 @@ Query | Example
|
||||
------------- | -------------
|
||||
`NOT` | **[hello NOT world](https://github.com/search?q=hello+NOT+world&type=Repositories)** matches repositories that have the word "hello" but not the word "world."
|
||||
|
||||
Another way you can narrow down search results is to exclude certain subsets. You can prefix any search qualifier with a `-` to exclude all results that are matched by that qualifier.
|
||||
|
||||
Query | Example
|
||||
------------- | -------------
|
||||
<code>-<em>QUALIFIER</em></code> | **[`cats stars:>10 -language:javascript`](https://github.com/search?q=cats+stars%3A>10+-language%3Ajavascript&type=Repositories)** matches repositories with the word "cats" that have more than 10 stars but are not written in JavaScript.
|
||||
<code>-<em>QUALIFIER</em></code> | **[`mentions:defunkt -org:github`](https://github.com/search?utf8=%E2%9C%93&q=mentions%3Adefunkt+-org%3Agithub&type=Issues)** matches issues mentioning @defunkt that are not in repositories in the GitHub organization
|
||||
|
||||
## Use quotation marks for queries with whitespace
|
||||
|
||||
If your search query contains whitespace, you will need to surround it with quotation marks. For example:
|
||||
|
||||
@@ -53,11 +53,12 @@ Style your CTAs using the following format.
|
||||
|
||||
### Code blocks
|
||||
|
||||
Keep lines in code samples to about 60 characters, to avoid requiring readers to scroll horizontally in the code block. Locate explanatory text before the code block, rather than using comments inside the code block.
|
||||
Keep lines in code samples to about 60 characters, to avoid requiring readers to scroll horizontally in the code block. Locate explanatory text before the code block, rather than using comments inside the code block. See "[Code sample syntax highlighting](./content-markup-reference.md#code-sample-syntax-highlighting)" for more information on the syntax and formatting of code blocks.
|
||||
|
||||
Within code blocks:
|
||||
- Do not use markup before the command output.
|
||||
- Only use `$` before the command itself if you’re showing the command’s output in the same block.
|
||||
- If you show a command and the command's output, do not make the code block copyable.
|
||||
- If your code example includes `{` or `}` that should render, wrap that section in `{% raw %}` `{% endraw %}` to disable Liquid processing for that section.
|
||||
- If your code example includes content that should be parsed (for example, HTML tags to format text), wrap that section in `<pre>` `</pre>` tags to parse rather than escape the content in the section.
|
||||
- **Use**:
|
||||
|
||||
Reference in New Issue
Block a user