jprdonnelly/docs
1
0
Fork 0
mirror of synced 2026-01-06 06:02:35 -05:00
Code Issues Projects Releases Wiki Activity

Fix trailing spaces in content and data (#37904)

Browse Source
This commit is contained in:
Grace Park
2023-06-23 10:45:10 -07:00
committed by GitHub
parent 07dcb8c294
commit cbda3f2434
369 changed files with 642 additions and 641 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
data/reusables/actions/comparing-artifacts-caching.md
View File

@@ -3,4 +3,4 @@
Artifacts and caching are similar because they provide the ability to store files on {% data variables.product.prodname_dotcom %}, but each feature offers different use cases and cannot be used interchangeably.
- Use caching when you want to reuse files that don't change often between jobs or workflow runs, such as build dependencies from a package management system.
- Use artifacts when you want to save files produced by a job to view after a workflow run has ended, such as built binaries or build logs.
- Use artifacts when you want to save files produced by a job to view after a workflow run has ended, such as built binaries or build logs.

2
data/reusables/actions/disable-selfhosted-runners-overview.md
View File

@@ -1,4 +1,4 @@
There is no guarantee that self-hosted runners for {% data variables.product.product_name %} will be hosted on ephemeral, clean virtual machines. As a result, they may be compromised by untrusted code in a workflow.
There is no guarantee that self-hosted runners for {% data variables.product.product_name %} will be hosted on ephemeral, clean virtual machines. As a result, they may be compromised by untrusted code in a workflow.
Similarly, anyone who can fork the repository and open a pull request (generally those with read access to the repository) can compromise the self-hosted runner environment, including gaining access to secrets and the `GITHUB_TOKEN` which, depending on its settings, can grant write access to the repository. Although workflows can control access to environment secrets by using environments and required reviews, these workflows are not run in an isolated environment and are still susceptible to the same risks when run on a self-hosted runner.

2
data/reusables/actions/example-docs-engineering-intro.md
View File

@@ -1 +1 @@
The following workflow was created by the {% data variables.product.prodname_dotcom %} Docs Engineering team. To review the latest version of this file in the [`github/docs`](https://github.com/github/docs) repository, see
The following workflow was created by the {% data variables.product.prodname_dotcom %} Docs Engineering team. To review the latest version of this file in the [`github/docs`](https://github.com/github/docs) repository, see

2
data/reusables/actions/example-workflow-intro-ci.md
View File

@@ -1 +1 @@
This article uses an example workflow to demonstrate some of the main CI features of {% data variables.product.prodname_actions %}.
This article uses an example workflow to demonstrate some of the main CI features of {% data variables.product.prodname_actions %}.

2
data/reusables/actions/general-security-hardening.md
View File

@@ -1,3 +1,3 @@
## General security hardening for {% data variables.product.prodname_actions %}
## General security hardening for {% data variables.product.prodname_actions %}
If you want to learn more about security practices for {% data variables.product.prodname_actions %}, see "[AUTOTITLE](/actions/security-guides/security-hardening-for-github-actions)."

2
data/reusables/actions/inputs-vs-github-event-inputs.md
View File

@@ -2,7 +2,7 @@
{% note %}
**Notes**:
**Notes**:
- The workflow will also receive the inputs in the `github.event.inputs` context. The information in the `inputs` context and `github.event.inputs` context is identical except that the `inputs` context preserves Boolean values as Booleans instead of converting them to strings. The `choice` type resolves to a string and is a single selectable option.
- The maximum number of top-level properties for `inputs` is 10.

2
data/reusables/actions/jobs/section-running-jobs-in-a-container-credentials.md
View File

@@ -1,6 +1,6 @@
{% data reusables.actions.registry-credentials %}
#### Example: Defining credentials for a container registry
#### Example: Defining credentials for a container registry
{% raw %}
```yaml

2
data/reusables/actions/jobs/using-matrix-strategy.md
View File

@@ -9,7 +9,7 @@ jobs:
os: [ubuntu-latest, windows-latest]
```
A job will run for each possible combination of the variables. In this example, the workflow will run six jobs, one for each combination of the `os` and `version` variables.
A job will run for each possible combination of the variables. In this example, the workflow will run six jobs, one for each combination of the `os` and `version` variables.
By default, {% data variables.product.product_name %} will maximize the number of jobs run in parallel depending on runner availability. The order of the variables in the matrix determines the order in which the jobs are created. The first variable you define will be the first job that is created in your workflow run. For example, the above matrix will create the jobs in the following order:

4
data/reusables/actions/runner-group-assign-policy-workflow.md
View File

@@ -1,6 +1,6 @@
{%- ifversion restrict-groups-to-workflows %}
1. Assign a policy for workflow access.
You can configure a runner group to be accessible to a specific list of workflows, or to all workflows. This setting can't be overridden if you are configuring an organization's runner group that was shared by an enterprise. If you specify what workflow can access the runner group, you must use the full path to the workflow, including the repository name and owner, and you must pin the workflow to a branch, tag, or full SHA. For example: `octo-org/octo-repo/.github/workflows/build.yml@v2, octo-org/octo-repo/.github/workflows/deploy.yml@d6dc6c96df4f32fa27b039f2084f576ed2c5c2a5, monalisa/octo-test/.github/workflows/test.yml@main`.
You can configure a runner group to be accessible to a specific list of workflows, or to all workflows. This setting can't be overridden if you are configuring an organization's runner group that was shared by an enterprise. If you specify what workflow can access the runner group, you must use the full path to the workflow, including the repository name and owner, and you must pin the workflow to a branch, tag, or full SHA. For example: `octo-org/octo-repo/.github/workflows/build.yml@v2, octo-org/octo-repo/.github/workflows/deploy.yml@d6dc6c96df4f32fa27b039f2084f576ed2c5c2a5, monalisa/octo-test/.github/workflows/test.yml@main`.
Only jobs directly defined within the selected workflows will have access to the runner group.{%- endif %}

2
data/reusables/actions/self-hosted-runner-management-permissions-required.md
View File

@@ -1,6 +1,6 @@
A self-hosted runner can be located in either your repository, organization, or {% ifversion fpt or ghec %}enterprise account settings on {% data variables.product.prodname_dotcom %}{% elsif ghes or ghae %} enterprise settings on {% data variables.location.product_location %}{% endif %}. To manage a self-hosted runner, you must have the following permissions, depending on where the self-hosted runner was added:
- **User repository**: You must be the repository owner.
- **Organization**: You must be an organization owner.
- **Organization**: You must be an organization owner.
- **Organization repository**: You must be an organization owner, or have admin access to the repository.
{% ifversion ghec %}
- **Enterprise account**: You must be an enterprise owner.

2
data/reusables/actions/self-hosted-runner-ports-protocols.md
View File

@@ -1,3 +1,3 @@
{% ifversion ghes or ghae %}
The connection between self-hosted runners and {% data variables.product.product_name %} is over {% ifversion ghes %}HTTP (port 80) or {% endif %}HTTPS (port 443). {% ifversion ghes %}To ensure connectivity over HTTPS, configure TLS for {% data variables.location.product_location %}. For more information, see "[AUTOTITLE](/admin/configuration/configuring-network-settings/configuring-tls)."{% endif %}
The connection between self-hosted runners and {% data variables.product.product_name %} is over {% ifversion ghes %}HTTP (port 80) or {% endif %}HTTPS (port 443). {% ifversion ghes %}To ensure connectivity over HTTPS, configure TLS for {% data variables.location.product_location %}. For more information, see "[AUTOTITLE](/admin/configuration/configuring-network-settings/configuring-tls)."{% endif %}
{% endif %}

2
data/reusables/actions/workflow-permissions-modifying.md
View File

@@ -1 +1 @@
Anyone with write access to a repository can modify the permissions granted to the `GITHUB_TOKEN`, adding or removing access as required, by editing the `permissions` key in the workflow file. For more information, see [`permissions`](/actions/using-workflows/workflow-syntax-for-github-actions#permissions).
Anyone with write access to a repository can modify the permissions granted to the `GITHUB_TOKEN`, adding or removing access as required, by editing the `permissions` key in the workflow file. For more information, see [`permissions`](/actions/using-workflows/workflow-syntax-for-github-actions#permissions).

2
data/reusables/advanced-security/secret-scanning-push-protection-enterprise.md
View File

@@ -1,5 +1,5 @@
1. Under "{% data variables.product.prodname_secret_scanning_caps %}", under "Push protection", click **Enable all**.
![Screenshot of the "Push protection" section of the "Code security and analysis" page. Two buttons, labeled "Enable all" and "Disable all", are highlighted with a dark orange outline.](/assets/images/enterprise/security/secret-scanning-enable-push-protection-enterprise.png)
2. Optionally, click "Automatically enable for repositories added to {% data variables.product.prodname_secret_scanning %}."{% ifversion secret-scanning-custom-link-on-block %}

2
data/reusables/apps/oauth-app-access-restrictions.md
View File

@@ -1 +1 @@
When {% data variables.product.prodname_oauth_app %} access restrictions are enabled, organization members and outside collaborators cannot authorize {% data variables.product.prodname_oauth_app %} access to organization resources. Organization members can request owner approval for {% data variables.product.prodname_oauth_apps %} they'd like to use, and organization owners receive a notification of pending requests.
When {% data variables.product.prodname_oauth_app %} access restrictions are enabled, organization members and outside collaborators cannot authorize {% data variables.product.prodname_oauth_app %} access to organization resources. Organization members can request owner approval for {% data variables.product.prodname_oauth_apps %} they'd like to use, and organization owners receive a notification of pending requests.

4
data/reusables/audit_log/git-events-export-limited.md
View File

@@ -1,7 +1,7 @@
{% ifversion ghec %}
{% note %}
**Note:** When you export Git events, events that were initiated via the web browser or the REST or GraphQL APIs are not included. For example, when a user merges a pull request in the web browser, changes are pushed to the base branch, but the Git event for that push is not included in the export.
**Note:** When you export Git events, events that were initiated via the web browser or the REST or GraphQL APIs are not included. For example, when a user merges a pull request in the web browser, changes are pushed to the base branch, but the Git event for that push is not included in the export.
{% endnote %}
{% endnote %}
{% endif %}

2
data/reusables/billing/edit-payment-method.md
View File

@@ -1,3 +1,3 @@
1. If your account has an existing payment method that you want to update, click **Edit**.
![Screenshot of the "Payment method" section. Next to "Payment method", a link, labeled "Edit", is outlined in dark orange.](/assets/images/help/billing/billing-payment-method-edit-button.png)

2
data/reusables/billing/email-notifications.md
View File

@@ -1,3 +1,3 @@
Email notifications are sent to account owners and billing managers when spending reaches 50%, 75%, 90% and 100% of your account's included usage and when spending reaches 50%, 75%, 90%, and 100% of your account's spending limit.
Email notifications are sent to account owners and billing managers when spending reaches 50%, 75%, 90% and 100% of your account's included usage and when spending reaches 50%, 75%, 90%, and 100% of your account's spending limit.
You can disable these notifications at any time by navigating to the "Email alerts" section at the bottom of the "Spending limit" page.

2
data/reusables/billing/license-statuses.md
View File

@@ -1,6 +1,6 @@
{% ifversion ghec %}
If your license includes {% data variables.visual_studio.prodname_vss_ghe %}, you can identify whether a user account on {% data variables.product.prodname_dotcom_the_website %} has successfully matched with a {% data variables.product.prodname_vs %} subscriber by downloading the CSV file that contains additional license details. The license status will be one of the following.
- "Matched": The user account on {% data variables.product.prodname_dotcom_the_website %} is linked with a {% data variables.product.prodname_vs %} subscriber.
- "Pending Invitation": An invitation was sent to a {% data variables.product.prodname_vs %} subscriber, but the subscriber has not accepted the invitation.
- "Pending Invitation": An invitation was sent to a {% data variables.product.prodname_vs %} subscriber, but the subscriber has not accepted the invitation.
- Blank: There is no {% data variables.product.prodname_vs %} association to consider for the user account on {% data variables.product.prodname_dotcom_the_website %}.
{% endif %}

2
data/reusables/classroom/supported-lmses.md
View File

@@ -5,7 +5,7 @@
Using LTI helps keep your information safe and secure. LTI is an industry-standard protocol and GitHub Classroom's use of LTI is certified by the Instructional Management System (IMS) Global Learning Consortium. For more information, see [Learning Tools Interoperability](https://www.imsglobal.org/activity/learning-tools-interoperability) and [About IMS Global Learning Consortium](http://www.imsglobal.org/aboutims.html) on the IMS Global Learning Consortium website.
{% data variables.product.company_short %} has tested and verified registration, connection and the import of roster data from the following LMSes into {% data variables.product.prodname_classroom %}.
{% data variables.product.company_short %} has tested and verified registration, connection and the import of roster data from the following LMSes into {% data variables.product.prodname_classroom %}.
- Canvas
- Moodle

2
data/reusables/classroom/you-can-choose-a-template-repository.md
View File

@@ -2,6 +2,6 @@ You can optionally choose a template repository as starter code for the assignme
{% note %}
**Note:** The template repository must belong to your organization or be a public repository on {% data variables.product.product_name %}.
**Note:** The template repository must belong to your organization or be a public repository on {% data variables.product.product_name %}.
{% endnote %}

2
data/reusables/code-scanning/beta-codeql-ml-queries.md
View File

@@ -2,7 +2,7 @@
{% note %}
**Note:** Experimental alerts for {% data variables.product.prodname_code_scanning %} are created using experimental technology in the {% data variables.product.prodname_codeql %} action. This feature is currently available as a beta release for JavaScript code and is subject to change.
**Note:** Experimental alerts for {% data variables.product.prodname_code_scanning %} are created using experimental technology in the {% data variables.product.prodname_codeql %} action. This feature is currently available as a beta release for JavaScript code and is subject to change.
{% endnote %}

2
data/reusables/code-scanning/example-configuration-files.md
View File

@@ -33,7 +33,7 @@ paths-ignore:
{% ifversion code-scanning-exclude-queries-from-analysis %}
The following configuration file only runs queries that generate alerts of severity error. The configuration first selects all the default queries, all queries in `./my-queries`, and the default suite in `codeql/java-queries`, then excludes all the queries that generate warnings or recommendations.
The following configuration file only runs queries that generate alerts of severity error. The configuration first selects all the default queries, all queries in `./my-queries`, and the default suite in `codeql/java-queries`, then excludes all the queries that generate warnings or recommendations.
``` yaml
queries:

2
data/reusables/codeql-cli/codeql-site-migration-note.md
View File

@@ -1,5 +1,5 @@
{% note %}
**Note:** This article was migrated from the [CodeQL documentation website](https://codeql.github.com/docs/codeql-cli/) in January 2023.
**Note:** This article was migrated from the [CodeQL documentation website](https://codeql.github.com/docs/codeql-cli/) in January 2023.
{% endnote %}

2
data/reusables/codespaces/changing-machine-type-in-vscode.md
View File

@@ -2,7 +2,7 @@
1. Search for and select "Codespaces: Change Machine Type."
![Screenshot of "change machine" entered as a search string and "Codespaces: Change Machine Type" in the dropdown list.](/assets/images/help/codespaces/vscode-change-machine-type-option.png)
1. If you're not following these instructions within a codespace, click the codespace that you want to change.
![Screenshot of a dropdown list of four codespaces.](/assets/images/help/codespaces/vscode-change-machine-choose-repo.png)

2
data/reusables/codespaces/codespaces-machine-types.md
View File

@@ -1,3 +1,3 @@
Typically, you can run your codespace on a choice of remote machine types. These machine types offer a choice of hardware specifications ranging from 2 cores to 32 cores, although the full range of machine types may not always be available. Each machine type has a different level of resources and a different billing tier. For information, see "[AUTOTITLE](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)."
By default the machine type with the lowest valid resources is used when you create a codespace.
By default the machine type with the lowest valid resources is used when you create a codespace.

2
data/reusables/codespaces/publishing-template-codespaces.md
View File

@@ -17,7 +17,7 @@ If you're working in a codespace, you can publish it from the {% data variables.
3. Click **Publish Branch**.
![Screenshot of the "Source control" side bar showing the "Publish Branch" button.](/assets/images/help/codespaces/vscode-publish-branch-button.png)
4. In the "Repository Name" dropdown, type a name for your new repository, then select **Publish to {% data variables.product.company_short %} private repository** or **Publish to {% data variables.product.company_short %} public repository**.
![Screenshot of the repository name dropdown in VS Code. Two options are shown, for publishing to a private or a public repository.](/assets/images/help/codespaces/choose-new-repository.png)

6
data/reusables/codespaces/source-control-pull-request.md
View File

@@ -1,9 +1,9 @@
1. After you've committed changes to your local copy of the repository, click the pull request icon at the top of the "Source Control" side bar.
1. After you've committed changes to your local copy of the repository, click the pull request icon at the top of the "Source Control" side bar.
![Screenshot of the top of the "Source Control" side bar. The pull request icon is highlighted with a dark orange outline.](/assets/images/help/codespaces/codespaces-commit-pr-button.png)
1. Check that the local branch and repository you're merging from, and the remote branch and repository you're merging into, are correct. Then give the pull request a title and a description.
1. Check that the local branch and repository you're merging from, and the remote branch and repository you're merging into, are correct. Then give the pull request a title and a description.
![Screenshot of the "{% data variables.product.prodname_dotcom %} Pull Request" side bar with a form for creating a pull request, including "Title" and "Description" fields.](/assets/images/help/codespaces/codespaces-commit-pr.png)
1. Click **Create**.

12
data/reusables/codespaces/source-control.md
View File

@@ -10,11 +10,11 @@ When you create a codespace from a template repository or a template on the "You
{% tip %}
**Tip**: If someone has recently changed a file on the remote repository, in the branch you switched to, you may not see those changes until you pull the changes into your codespace.
**Tip**: If someone has recently changed a file on the remote repository, in the branch you switched to, you may not see those changes until you pull the changes into your codespace.
{% endtip %}
## Committing your changes
## Committing your changes
{% data reusables.codespaces.source-control-activity-bar %}
1. To stage your changes, click {% octicon "plus" aria-label="Stage changes" %} next to the file you've changed, or next to **Changes** if you've changed multiple files and you want to stage them all.
@@ -31,7 +31,7 @@ When you create a codespace from a template repository or a template on the "You
## Pulling changes from the remote repository
You can pull changes from the remote repository into your codespace at any time.
You can pull changes from the remote repository into your codespace at any time.
{% data reusables.codespaces.source-control-activity-bar %}
1. At the top of the side bar, click {% octicon "kebab-horizontal" aria-label="Views and More Actions..." %}.
@@ -42,9 +42,9 @@ You can pull changes from the remote repository into your codespace at any time.
If the dev container configuration has been changed since you created the codespace, you can apply the changes by rebuilding the container for the codespace. For more information, see "[AUTOTITLE](/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/introduction-to-dev-containers#applying-changes-to-your-configuration)."
## Setting your codespace to automatically fetch new changes
## Setting your codespace to automatically fetch new changes
You can set your codespace to automatically fetch details of any new commits that have been made to the remote repository. This allows you to see whether your local copy of the repository is out of date, in which case you may choose to pull in the new changes.
You can set your codespace to automatically fetch details of any new commits that have been made to the remote repository. This allows you to see whether your local copy of the repository is out of date, in which case you may choose to pull in the new changes.
If the fetch operation detects new changes on the remote repository, you'll see the number of new commits in the status bar. You can then pull the changes into your local copy.
@@ -65,7 +65,7 @@ If the fetch operation detects new changes on the remote repository, you'll see
## Raising a pull request
{% data reusables.codespaces.source-control-pull-request %}
{% data reusables.codespaces.source-control-pull-request %}
## Pushing changes to your remote repository

2
data/reusables/codespaces/usage-report-download.md
View File

@@ -2,7 +2,7 @@
![Screenshot of the "Billing and plans" settings. A button, labeled "Get usage report", is highlighted with an orange outline.](/assets/images/help/billing/actions-packages-report-download.png)
The data used for this report is updated daily.
The data used for this report is updated daily.
To see the costs for {% data variables.product.prodname_github_codespaces %} compute usage and storage, filter the report to show only rows that mention "Codespaces" in the `Product` column.

2
data/reusables/command-palette/open-palette.md
View File

@@ -1 +1 @@
1. Use <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows/Linux) or <kbd>Command</kbd>+<kbd>K</kbd> (Mac) to open the command palette with a scope determined by your current location in the UI.
1. Use <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows/Linux) or <kbd>Command</kbd>+<kbd>K</kbd> (Mac) to open the command palette with a scope determined by your current location in the UI.

2
data/reusables/command_line/start_ssh_agent.md
View File

@@ -1,4 +1,4 @@
1. Start the ssh-agent in the background.
1. Start the ssh-agent in the background.
```shell
$ eval "$(ssh-agent -s)"

2
data/reusables/copilot/differences-cfi-cfb-table.md
View File

@@ -13,4 +13,4 @@
{% endrowheaders %}
For more information about VPN Proxy support via self-signed certificates, see "[AUTOTITLE](/copilot/configuring-github-copilot/configuring-github-copilot-in-your-environment?tool=vscode#configuring-proxy-settings-for-github-copilot-1)".
For more information about VPN Proxy support via self-signed certificates, see "[AUTOTITLE](/copilot/configuring-github-copilot/configuring-github-copilot-in-your-environment?tool=vscode#configuring-proxy-settings-for-github-copilot-1)".

1
data/reusables/copilot/type-function-header.md
View File

@@ -3,4 +3,3 @@
```javascript copy
function calculateDaysBetweenDates(begin, end) {
```

4
data/reusables/dependabot/dependabot-alerts-filters.md
View File

@@ -1,6 +1,6 @@
You can sort and filter {% data variables.product.prodname_dependabot_alerts %} by typing filters as `key:value` pairs into the search bar.
You can sort and filter {% data variables.product.prodname_dependabot_alerts %} by typing filters as `key:value` pairs into the search bar.
| Option | Description | Example |
| Option | Description | Example |
|:---|:---|:---|
| `ecosystem` | Displays alerts for the selected ecosystem | Use `ecosystem:npm` to show {% data variables.product.prodname_dependabot_alerts %} for npm |{% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
| `has` | Displays alerts meeting the selected filter criteria | Use `has:patch` to show alerts related to advisories that have a patch{% ifversion dependabot-alerts-vulnerable-calls %}</br>Use `has:vulnerable-calls` to show alerts relating to calls to vulnerable functions{% endif %} |{% endif %}

2
data/reusables/dependabot/private-registry-support.md
View File

@@ -1 +1 @@
{% data variables.product.prodname_dependabot %} can access public registries by default, and you can configure {% data variables.product.prodname_dependabot %} to also access private registries.
{% data variables.product.prodname_dependabot %} can access public registries by default, and you can configure {% data variables.product.prodname_dependabot %} to also access private registries.

2
data/reusables/dependabot/pull-request-security-vs-version-updates.md
View File

@@ -1,4 +1,4 @@
When {% data variables.product.prodname_dependabot %} raises pull requests, these pull requests could be for _security_ or _version_ updates:
- _{% data variables.product.prodname_dependabot_security_updates %}_ are automated pull requests that help you update dependencies with known vulnerabilities.
- _{% data variables.product.prodname_dependabot_security_updates %}_ are automated pull requests that help you update dependencies with known vulnerabilities.
- _{% data variables.product.prodname_dependabot_version_updates %}_ are automated pull requests that keep your dependencies updated, even when they don’t have any vulnerabilities. To check the status of version updates, navigate to the Insights tab of your repository, then Dependency Graph, and {% data variables.product.prodname_dependabot %}.

2
data/reusables/dependabot/vulnerable-calls-beta.md
View File

@@ -2,7 +2,7 @@
{% note %}
**Notes:**
**Notes:**
- The detection of calls to vulnerable functions by {% data variables.product.prodname_dependabot %} is in beta and subject to change.

2
data/reusables/dependency-submission/about-dependency-submission.md
View File

@@ -1,5 +1,5 @@
You can use the REST API to submit dependencies for a project. This enables you to add dependencies, such as those resolved when software is compiled or built, to {% data variables.product.prodname_dotcom %}'s dependency graph feature, providing a more complete picture of all of your project's dependencies.
The dependency graph shows any dependencies you submit using the API in addition to any dependencies that are identified from manifest or lock files in the repository (for example, a `package-lock.json` file in a JavaScript project). For more information about viewing the dependency graph, see "[AUTOTITLE](/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository#viewing-the-dependency-graph)."
The dependency graph shows any dependencies you submit using the API in addition to any dependencies that are identified from manifest or lock files in the repository (for example, a `package-lock.json` file in a JavaScript project). For more information about viewing the dependency graph, see "[AUTOTITLE](/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository#viewing-the-dependency-graph)."
Submitted dependencies will receive {% data variables.product.prodname_dependabot_alerts %} and {% data variables.product.prodname_dependabot_security_updates %} for any known vulnerabilities. You will only get {% data variables.product.prodname_dependabot_alerts %} for dependencies that are from one of the [supported ecosystems](https://github.com/github/advisory-database#supported-ecosystems) of the {% data variables.product.prodname_advisory_database %}. Submitted dependencies will not be surfaced in dependency review or your organization's dependency insights.

2
data/reusables/desktop/authenticate-in-browser.md
View File

@@ -1,3 +1,3 @@
1. To authenticate to {% data variables.product.prodname_dotcom %}, in the browser, type your {% data variables.product.prodname_dotcom %}.com credentials and click **Sign in**.
Alternatively, if you were already signed in to {% data variables.product.prodname_dotcom %}, follow the prompts to return to {% data variables.product.prodname_desktop %} to finish authenticating.
Alternatively, if you were already signed in to {% data variables.product.prodname_dotcom %}, follow the prompts to return to {% data variables.product.prodname_desktop %} to finish authenticating.

2
data/reusables/desktop/choose-a-theme.md
View File

@@ -1,7 +1,7 @@
3. Click the **Appearance** pane.
{% mac %}
![Screenshot of the "Preferences" window. In the left sidebar, the "Appearance" option is highlighted in blue and outlined in orange.](/assets/images/help/desktop/appearance-tab-themes.png)
{% endmac %}

2
data/reusables/desktop/fork-type-prompt.md
View File

@@ -1,4 +1,4 @@
1. Read the information in the "How are you planning to use this fork?" window.
1. Read the information in the "How are you planning to use this fork?" window.
- If you plan to use this fork for contributing to the original upstream repository, click **To contribute to the parent project**.
- If you plan to use this fork for a project not connected to the upstream, click **For my own purposes**.
1. Click **Continue**.

2
data/reusables/desktop/history-tab.md
View File

@@ -1,3 +1,3 @@
1. In the left sidebar, click **History**.
![Screenshot of the "History" tab in the sidebar. Above a list of commits, the tab button, labeled "History", is highlighted with an orange outline.](/assets/images/help/desktop/history-tab-in-commit-sidebar.png)

2
data/reusables/desktop/mac-repository-settings-menu.md
View File

@@ -1,3 +1,3 @@
1. In the "{% data variables.product.prodname_desktop %}" menu bar, select **Repository** and click **Repository Settings...**.
![Screenshot of the menu bar on a Mac. In the open "Repository" dropdown menu, a cursor hovers over "Repository Settings", highlighted in blue.](/assets/images/help/desktop/repository-settings-mac.png)

10
data/reusables/desktop/open-repository-settings.md
View File

@@ -1,14 +1,14 @@
1. In the menu bar, select **Repository**, then click **Repository settings...**.
{% mac %}
![Screenshot of the menu bar on a Mac. In the expanded "Repository" dropdown menu, a cursor hovers over "Repository Settings", highlighted in blue.](/assets/images/help/desktop/repository-settings-mac.png)
{% endmac %}
{% windows %}
![Screenshot of the "GitHub Desktop" menu bar on Windows. In the open "Repository" dropdown menu, an option labeled "Repository Settings" is outlined in orange.](/assets/images/help/desktop/repository-settings-win.png)
{% endwindows %}

2
data/reusables/desktop/push-origin.md
View File

@@ -1,3 +1,3 @@
1. To push your local changes to the remote repository, in the repository bar, click **Push origin**.
![Screenshot of the repository bar. A button, labeled "Push origin", is highlighted with an orange outline.](/assets/images/help/desktop/push-to-origin.png)

2
data/reusables/desktop/select-fork-behavior.md
View File

@@ -1,4 +1,4 @@
1. In the "Repository settings" window, in the left-hand sidebar, click **Fork Behavior**.
1. In the "Repository settings" window, in the left-hand sidebar, click **Fork Behavior**.
1. Under "I'll be using this fork...", use the radio buttons to select how you want to use the fork.
![Screenshot of the "Fork Behavior" pane. Two radio buttons, labeled "To contribute to the parent repository" and "For my own purposes", are outlined in orange.](/assets/images/help/desktop/mac-fork-behavior-menu-contribute.png)

2
data/reusables/desktop/windows-choose-options.md
View File

@@ -1,3 +1,3 @@
1. Use the **File** menu, then click **Options**.
![Screenshot of the "GitHub Desktop" menu bar on Windows. In the expanded "File" dropdown menu, the "Options" item is highlighted with an orange outline.](/assets/images/help/desktop/windows-choose-options.png)

2
data/reusables/desktop/windows-repository-settings-menu.md
View File

@@ -1,3 +1,3 @@
1. In the **Repository** menu, click **Repository settings...**.
![Screenshot of the "GitHub Desktop" menu bar on Windows. In the open "Repository" dropdown menu, an option labeled "Repository Settings" is outlined in orange.](/assets/images/help/desktop/repository-settings-win.png)

2
data/reusables/discussions/discussion-category-forms-name.md
View File

@@ -1 +1 @@
The name must correspond with the slug for one of your discussion categories. For example, the template for the "Announcements" category should be `.github/DISCUSSION_TEMPLATE/announcements.yml`.
The name must correspond with the slug for one of your discussion categories. For example, the template for the "Announcements" category should be `.github/DISCUSSION_TEMPLATE/announcements.yml`.

2
data/reusables/education/benefits-page.md
View File

@@ -1 +1 @@
1. Go to [{% data variables.product.prodname_education %}](https://education.github.com) and, in the top navigation bar, click **Benefits**.
1. Go to [{% data variables.product.prodname_education %}](https://education.github.com) and, in the top navigation bar, click **Benefits**.

2
data/reusables/education/note-on-student-codespaces-usage.md
View File

@@ -1 +1 @@
If students use {% data variables.product.prodname_github_codespaces %} in their assignment repositories for {% data variables.product.prodname_classroom %}, the usage will be charged to the organization that owns the classroom, and will not affect the usage for a student's personal account.
If students use {% data variables.product.prodname_github_codespaces %} in their assignment repositories for {% data variables.product.prodname_classroom %}, the usage will be charged to the organization that owns the classroom, and will not affect the usage for a student's personal account.

2
data/reusables/enterprise-accounts/emu-azure-admin-consent.md
View File

@@ -1,4 +1,4 @@
1. After {% data variables.product.product_name %} redirects you to your IdP, sign in, then follow the instructions to give consent and install the {% data variables.product.prodname_emu_idp_oidc_application %} application. After Azure AD asks for permissions for {% data variables.product.company_short %} {% data variables.product.prodname_emus %} with OIDC, enable **Consent on behalf of your organization**, then click **Accept**.
1. After {% data variables.product.product_name %} redirects you to your IdP, sign in, then follow the instructions to give consent and install the {% data variables.product.prodname_emu_idp_oidc_application %} application. After Azure AD asks for permissions for {% data variables.product.company_short %} {% data variables.product.prodname_emus %} with OIDC, enable **Consent on behalf of your organization**, then click **Accept**.
{% warning %}
**Warning:** You must sign in to Azure AD as a user with global admin rights in order to consent to the installation of the {% data variables.product.prodname_emu_idp_oidc_application %} application.

2
data/reusables/enterprise-migration-tool/check-migration.md
View File

@@ -22,6 +22,6 @@ query (
}
```
| Query variable | Description |
| Query variable | Description |
|----|----|
| `id` | The `id` of your migration that [the `startRepositoryMigration` mutation](#step-4-start-your-repository-migration) returned. |

2
data/reusables/enterprise-migration-tool/edit-csv.md
View File

@@ -1,2 +1,2 @@
- Edit the CSV file, adding the username of the organization member that corresponds to each mannequin.
- Edit the CSV file, adding the username of the organization member that corresponds to each mannequin.
- Save the file.

2
data/reusables/enterprise-migration-tool/migration-destination-query.md
View File

@@ -14,7 +14,7 @@ query(
}
```
| Query variable | Description |
| Query variable | Description |
|----|----|
| `login` | Your organization name.

2
data/reusables/enterprise-migration-tool/reclaim-individual-mannequin.md
View File

@@ -1,3 +1,3 @@
- To reclaim an individual mannequin, replace DESTINATION with the destination organization, MANNEQUIN with the login of mannequin, and USERNAME with the username of the organization member that corresponds to the mannequin.
If there are multiple mannequins with the same login, you can replace `--mannequin-user MANNEQUIN` with `--mannequin-ID ID`, replacing ID with the ID of the mannequin.
If there are multiple mannequins with the same login, you can replace `--mannequin-user MANNEQUIN` with `--mannequin-ID ID`, replacing ID with the ID of the mannequin.

2
data/reusables/enterprise-migration-tool/running-your-migrations.md
View File

@@ -6,4 +6,4 @@ Trial migrations help you determine several critical pieces of information.
- Whether you can get the repository back to a state where your users can successfully start working
- How long a migration will take to run, which is useful for planning migration schedules and setting stakeholder expectations
Trial runs do not require much time coordination. {% data variables.product.prodname_importer_proper_name %} never requires downtime for users of a repository being migrated. However, we recommend halting work during production migrations to ensure that new data isn't created during the migration, which would then be missing from the migrated repository. This isn't a concern for trial migrations, so trial runs can take place at any time. To reduce the time it takes to complete your trial migrations, you can schedule the batches for your trial runs back-to-back. Users of those repositories can then validate the results on their own time.
Trial runs do not require much time coordination. {% data variables.product.prodname_importer_proper_name %} never requires downtime for users of a repository being migrated. However, we recommend halting work during production migrations to ensure that new data isn't created during the migration, which would then be missing from the migrated repository. This isn't a concern for trial migrations, so trial runs can take place at any time. To reduce the time it takes to complete your trial migrations, you can schedule the batches for your trial runs back-to-back. Users of those repositories can then validate the results on their own time.

2
data/reusables/enterprise-migration-tool/skip-releases.md
View File

@@ -2,4 +2,4 @@
**Note:** If your repository has more than 10 GB of releases data, releases cannot be migrated. Use the `--skip-releases` flag to migrate the repository without releases.
{% endnote %}
{% endnote %}

2
data/reusables/enterprise-migration-tool/ssl-flag.md
View File

@@ -1 +1 @@
If {% data variables.location.product_location_enterprise %} uses a self-signed or invalid SSL certificate, use the `--no-ssl-verify` flag. With this flag, the {% data variables.product.prodname_cli %} will skip verifying the SSL certificate when extracting data from your instance only. All other calls will verify SSL.
If {% data variables.location.product_location_enterprise %} uses a self-signed or invalid SSL certificate, use the `--no-ssl-verify` flag. With this flag, the {% data variables.product.prodname_cli %} will skip verifying the SSL certificate when extracting data from your instance only. All other calls will verify SSL.

2
data/reusables/enterprise-migration-tool/timeline-tasks.md
View File

@@ -1,4 +1,4 @@
After you use the analyzer, you can weigh your inventory data against your desired timeline. If your organization can withstand a higher degree of change, then you might be able to migrate all your repositories at once, completing your migration efforts in a few days. However, you may have various teams that are not able to migrate at the same time. In this case, you might want to batch and stagger your migrations to fit the teams' timelines, extending your migration effort.
After you use the analyzer, you can weigh your inventory data against your desired timeline. If your organization can withstand a higher degree of change, then you might be able to migrate all your repositories at once, completing your migration efforts in a few days. However, you may have various teams that are not able to migrate at the same time. In this case, you might want to batch and stagger your migrations to fit the teams' timelines, extending your migration effort.
1. Use the [{% data variables.product.company_short %} Migration Analyzer](https://github.com/github/gh-migration-analyzer), then review your migration inventory.
1. To understand when teams can be ready to migrate, interview stakeholders.

2
data/reusables/enterprise/apply-configuration.md
View File

@@ -1,7 +1,7 @@
1. To apply the configuration, run the following command.
{% note %}
**Note**: During a configuration run, services on {% data variables.location.product_location %} may restart, which can cause brief downtime for users.
{% endnote %}

4
data/reusables/enterprise_site_admin_settings/create-pgp-key-web-commit-signing.md
View File

@@ -3,5 +3,5 @@
```bash copy
gpg --full-generate-key --pinentry-mode=loopback
```
- Use the default key type and at least `4096` bits with no expiry.
- Use the default key type and at least `4096` bits with no expiry.

2
data/reusables/enterprise_user_management/SAML-to-OIDC-migration-for-EMU.md
View File

@@ -1 +1 @@
If you currently use SAML SSO for authentication and would prefer to use OIDC and benefit from CAP support, you can follow a migration path. For more information, see "[AUTOTITLE](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc)."
If you currently use SAML SSO for authentication and would prefer to use OIDC and benefit from CAP support, you can follow a migration path. For more information, see "[AUTOTITLE](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc)."

2
data/reusables/files/add-file.md
View File

@@ -1,6 +1,6 @@
{% ifversion code-search-code-view %}
1. Above the list of files, select the **Add file** {% octicon "triangle-down" aria-label="The downwards-facing triangle icon" %} dropdown menu, then click {% octicon "plus" aria-label="The plus sign icon" %} **Create new file**.
Alternatively, you can click {% octicon "plus" aria-label="The plus sign icon" %} in the file tree view on the left.
![Screenshot of the main page of the repository. Above the list of a files, a button, labeled "Add file," is outlined in dark orange. In the file tree view of the repository, a button, with the plus sign icon, is also outlined in dark orange. ](/assets/images/help/repository/add-files-buttons.png)

2
data/reusables/gated-features/codeql.md
View File

@@ -1,3 +1,3 @@
GitHub {% data variables.product.prodname_codeql %} is licensed on a per-user basis upon installation. You can use {% data variables.product.prodname_codeql %} only for certain tasks under the license restrictions. For more information, see "[AUTOTITLE](/code-security/codeql-cli/using-the-codeql-cli/about-the-codeql-cli#about-the-github-codeql-license)."
If you have a GitHub Advanced Security license, you can use {% data variables.product.prodname_codeql %} for automated analysis, continuous integration, and continuous delivery. {% data reusables.advanced-security.more-info-ghas %}

10
data/reusables/gated-features/dependabot-alerts.md
View File

@@ -1,10 +1,10 @@
{%- ifversion fpt or ghec %}
{%- ifversion fpt or ghec %}
{% data variables.product.prodname_dependabot_alerts %} are free to use for all repositories on {% data variables.product.prodname_dotcom_the_website %}.
{%- elsif ghes %}
{% data variables.product.prodname_dependabot_alerts %} are free to use for repositories (user-owned and organization-owned) on {% data variables.product.prodname_ghe_server %}, provided enterprise administrators enable the feature for your enterprise.
{%- elsif ghes %}
{% data variables.product.prodname_dependabot_alerts %} are free to use for repositories (user-owned and organization-owned) on {% data variables.product.prodname_ghe_server %}, provided enterprise administrators enable the feature for your enterprise.
{%- elsif ghae %}
{% data variables.product.prodname_dependabot_alerts %} are free to use for repositories (user-owned and organization-owned) on {% data variables.product.prodname_ghe_managed %}.
{%- elsif ghae %}
{% data variables.product.prodname_dependabot_alerts %} are free to use for repositories (user-owned and organization-owned) on {% data variables.product.prodname_ghe_managed %}.
{% endif %}

6
data/reusables/gated-features/dependabot-security-updates.md
View File

@@ -1,7 +1,7 @@
{%- ifversion fpt or ghec %}
{%- ifversion fpt or ghec %}
{% data variables.product.prodname_dependabot_security_updates %} are free to use for all repositories on {% data variables.product.prodname_dotcom_the_website %}.
{%- else %}
{% data variables.product.prodname_dependabot_security_updates %} are free to use for repositories (user-owned and organization-owned) on {% data variables.product.prodname_ghe_server %}, provided enterprise administrators enable the feature for your enterprise.
{%- else %}
{% data variables.product.prodname_dependabot_security_updates %} are free to use for repositories (user-owned and organization-owned) on {% data variables.product.prodname_ghe_server %}, provided enterprise administrators enable the feature for your enterprise.
{% endif %}

6
data/reusables/gated-features/dependabot-version-updates.md
View File

@@ -1,7 +1,7 @@
{%- ifversion fpt or ghec %}
{%- ifversion fpt or ghec %}
{% data variables.product.prodname_dependabot_version_updates %} are free to use for all repositories on {% data variables.product.prodname_dotcom_the_website %}.
{%- else %}
{% data variables.product.prodname_dependabot_version_updates %} are free to use for repositories (user-owned and organization-owned) on {% data variables.product.prodname_ghe_server %}, provided enterprise administrators enable the feature for your enterprise.
{%- else %}
{% data variables.product.prodname_dependabot_version_updates %} are free to use for repositories (user-owned and organization-owned) on {% data variables.product.prodname_ghe_server %}, provided enterprise administrators enable the feature for your enterprise.
{% endif %}

2
data/reusables/gated-features/enterprise_account_webhooks.md
View File

@@ -1,4 +1,4 @@
{% data reusables.gated-features.enterprise-accounts %}
{% data reusables.gated-features.enterprise-accounts %}
Webhooks configured on enterprise accounts or organizations that are part of an enterprise account will include an `enterprise` account object.

4
data/reusables/gated-features/packages.md
View File

@@ -1,6 +1,6 @@
{% ifversion fpt or ghec or ghes < 3.5 %}
{% ifversion fpt or ghec or ghes < 3.5 %}
{% data variables.product.prodname_registry %} is available with {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_free_team %} for organizations, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_ghe_server %} 3.0 or higher, and {% data variables.product.prodname_ghe_managed %}.{% ifversion ghes %} For more information about upgrading your {% data variables.product.prodname_ghe_server %} instance, see "[AUTOTITLE](/admin/overview/about-upgrades-to-new-releases)" and refer to the [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) to find the upgrade path from your current release version.{% endif %}
{% ifversion fpt or ghec %}
{% ifversion fpt or ghec %}
<br>{% data variables.product.prodname_registry %} is not available for private repositories owned by accounts using legacy per-repository plans. Also, accounts using legacy per-repository plans cannot access registries that support granular permissions, because these accounts are billed by repository. For the list of registries that support granular permissions, see "[AUTOTITLE](/packages/learn-github-packages/about-permissions-for-github-packages#granular-permissions-for-userorganization-scoped-packages)." {% data reusables.gated-features.more-info %}
{% endif %}
{% endif %}

2
data/reusables/gpg/list-keys-with-note.md
View File

@@ -3,7 +3,7 @@
```shell copy
$ gpg --list-secret-keys --keyid-format=long
```
{% note %}
**Note:** Some GPG installations on Linux may require you to use `gpg2 --list-keys --keyid-format LONG` to view a list of your existing keys instead. In this case you will also need to configure Git to use `gpg2` by running `git config --global gpg.program gpg2`.

2
data/reusables/gpg/paste-gpg-key-id.md
View File

@@ -2,7 +2,7 @@
```shell
$ git config --global user.signingkey 3AA5C34371567BD2
```
Alternatively, when setting a subkey include the `!` suffix. In this example, the GPG subkey ID is `4BB6D45482678BE3`:
```shell
$ git config --global user.signingkey 4BB6D45482678BE3!

2
data/reusables/gpg/set-auto-sign.md
View File

@@ -3,5 +3,5 @@
```Shell
$ git config --global commit.gpgsign true
```
For more information, see "[AUTOTITLE](/authentication/managing-commit-signature-verification/signing-commits)."

2
data/reusables/identity-and-permissions/about-editing-ip-allow-list-entries.md
View File

@@ -1,3 +1,3 @@
You can edit an entry in your IP allow list. If you edit an enabled entry, changes are enforced immediately.
You can edit an entry in your IP allow list. If you edit an enabled entry, changes are enforced immediately.
After you finish editing entries, you can check whether your allow list will permit a connection from a particular IP address after you enable the list.

2
data/reusables/identity-and-permissions/about-enabling-allowed-ip-addresses.md
View File

@@ -3,7 +3,7 @@ After you create an IP allow list, you can enable allowed IP addresses. When you
{% ifversion ghec %}
{% note %}
**Note:**
**Note:**
After you enable an IP allow list for your organization you won't be able to use {% data variables.product.prodname_github_codespaces %} for repositories owned by the organization.

2
data/reusables/identity-and-permissions/ip-allow-lists-enterprise.md
View File

@@ -1,4 +1,4 @@
When you enable the allow list, the IP addresses you have configured are immediately added to the allow lists of organizations in your enterprise. If you disable the allow list, the addresses are removed from the organization allow lists.
When you enable the allow list, the IP addresses you have configured are immediately added to the allow lists of organizations in your enterprise. If you disable the allow list, the addresses are removed from the organization allow lists.
{% data reusables.identity-and-permissions.org-enterprise-allow-list-interaction %} For more information, see "[AUTOTITLE](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization)."

2
data/reusables/identity-and-permissions/org-enterprise-allow-list-interaction.md
View File

@@ -1 +1 @@
Organization owners can add additional entries to the allow list for their organizations, but they cannot manage entries that are inherited from the enterprise account's allow list, and enterprise owners cannot manage entries added to the organization's allow list.
Organization owners can add additional entries to the allow list for their organizations, but they cannot manage entries that are inherited from the enterprise account's allow list, and enterprise owners cannot manage entries added to the organization's allow list.

2
data/reusables/identity-and-permissions/vigilant-mode-verification-statuses.md
View File

@@ -1,5 +1,5 @@
| Status | Description |
| -------------- | ----------- |
| **Verified** | The commit is signed, the signature was successfully verified, and the committer is the only author who has enabled vigilant mode.
| **Verified** | The commit is signed, the signature was successfully verified, and the committer is the only author who has enabled vigilant mode.
| **Partially&nbsp;verified** | The commit is signed, and the signature was successfully verified, but the commit has an author who: a) is not the committer and b) has enabled vigilant mode. In this case, the commit signature doesn't guarantee the consent of the author, so the commit is only partially verified.
| **Unverified** | Any of the following is true:<br>- The commit is signed but the signature could not be verified.<br>- The commit is not signed and the committer has enabled vigilant mode.<br>- The commit is not signed and an author has enabled vigilant mode.<br>

2
data/reusables/issue-events/label-properties.md
View File

@@ -1,3 +1,3 @@
`label` | `object` | The label removed from the issue
`label[name]` | `string` | The name of the label.
`label[color]` | `string` | The hex color code.
`label[color]` | `string` | The hex color code.

2
data/reusables/issue-events/review-request-properties.md
View File

@@ -1,2 +1,2 @@
`requested_reviewer` | `object` | The person requested to review the pull request.
`requested_reviewer` | `object` | The person requested to review the pull request.
`review_requester` | `object` | The person who requested a review.

2
data/reusables/notifications-v2/email-notification-caveats.md
View File

@@ -1,4 +1,4 @@
You'll only receive notification emails if you've chosen to receive email notifications in your notification settings.
You'll only receive notification emails if you've chosen to receive email notifications in your notification settings.
{% ifversion fpt or ghec %}
{% data reusables.user-settings.verify-org-approved-email-domain %}

2
data/reusables/organizations/about-organizations.md
View File

@@ -1,3 +1,3 @@
Your team can collaborate on {% data variables.product.product_name %} by using an organization account, which serves as a container for your shared work and gives the work a unique name and brand.
Your team can collaborate on {% data variables.product.product_name %} by using an organization account, which serves as a container for your shared work and gives the work a unique name and brand.
Each person that uses {% data variables.product.prodname_dotcom %} always signs into a personal account, and multiple personal accounts can collaborate on shared projects by joining the same organization account. A subset of these personal accounts can be given the role of organization owner, which allows those people to granularly manage access to the organization's resources using sophisticated security and administrative features.

2
data/reusables/organizations/team-discussions-migration.md
View File

@@ -1,7 +1,7 @@
{% note %}
**Note**: Team discussions will be deprecated in {% data variables.product.prodname_ghe_server %} 3.12 in favor of {% data variables.product.prodname_discussions %}. You can transfer your existing team discussions to a repository's discussions by using a migration tool that allows team admins to migrate both public and private team discussions. Click the "Transfer" button in the banner at the top of your team discussions page, then choose the repository in your organization that you want to migrate the discussions to.
**Note**: Team discussions will be deprecated in {% data variables.product.prodname_ghe_server %} 3.12 in favor of {% data variables.product.prodname_discussions %}. You can transfer your existing team discussions to a repository's discussions by using a migration tool that allows team admins to migrate both public and private team discussions. Click the "Transfer" button in the banner at the top of your team discussions page, then choose the repository in your organization that you want to migrate the discussions to.
For more information about {% data variables.product.prodname_discussions %}, see "[AUTOTITLE](/discussions)."

2
data/reusables/package_registry/about-graphql-support.md
View File

@@ -1,3 +1,3 @@
{% ifversion packages-registries-v2 %}For certain registries, you{% else %}You{% endif %} can use GraphQL to delete a version of a private package.
{% ifversion packages-registries-v2 %}For certain registries, you{% else %}You{% endif %} can use GraphQL to delete a version of a private package.
{% data reusables.package_registry.no-graphql-to-delete-packages %}

2
data/reusables/package_registry/authenticate-to-container-registry-steps.md
View File

@@ -3,7 +3,7 @@
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 %}
**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 %}

2
data/reusables/package_registry/container-registry-ghes-beta.md
View File

@@ -2,7 +2,7 @@
{% note %}
**Note**: {% data variables.product.prodname_container_registry %} is currently in beta for {% data variables.product.product_name %} and subject to change.
**Note**: {% data variables.product.prodname_container_registry %} is currently in beta for {% data variables.product.product_name %} and subject to change.
Both {% data variables.product.prodname_registry %} and subdomain isolation must be enabled to use {% data variables.product.prodname_container_registry %}. For more information, see "[AUTOTITLE](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)."

2
data/reusables/pages/about-private-publishing.md
View File

@@ -1,5 +1,5 @@
{% ifversion fpt %}
You can create {% data variables.product.prodname_pages %} sites that are publicly available on the internet. Organizations that use {% data variables.product.prodname_ghe_cloud %} can also publish sites privately by managing access control for the site.
{% elsif ghec %}
Unless your enterprise uses {% data variables.product.prodname_emus %}, you can choose to publish project sites publicly or privately by managing access control for the site.
Unless your enterprise uses {% data variables.product.prodname_emus %}, you can choose to publish project sites publicly or privately by managing access control for the site.
{% endif %}

2
data/reusables/pages/admin-must-push.md
View File

@@ -1,6 +1,6 @@
{% note %}
**Notes**:
**Notes**:
- {% ifversion pages-custom-workflow %}If you are publishing from a branch and{% else %}If{% endif %} your site has not published automatically, make sure someone with admin permissions and a verified email address has pushed to the publishing source.

2
data/reusables/profile/navigating-to-profile.md
View File

@@ -1 +1 @@
1. In the upper-right corner of any {% data variables.product.product_name %} page, click your profile photo, then click **Your profile**.
1. In the upper-right corner of any {% data variables.product.product_name %} page, click your profile photo, then click **Your profile**.

2
data/reusables/projects/about-board-layout.md
View File

@@ -1,3 +1,3 @@
The board layout spreads your issues, pull requests, and draft issues across customizable columns. You can create a kanban board by setting your column field to a "Status" field or set any other single select or iteration field as the column field.
The board layout spreads your issues, pull requests, and draft issues across customizable columns. You can create a kanban board by setting your column field to a "Status" field or set any other single select or iteration field as the column field.
You can drag {% ifversion projects-v2-board-drag-multiple %}individual or multiple items{% else %}items{% endif %} from column to column and the value of {% ifversion projects-v2-board-drag-multiple %}those items{% else %}the item{% endif %} will adjust to match the column you drag them to.

2
data/reusables/projects/about-table-layout.md
View File

@@ -1 +1 @@
The table layout is a powerful and adaptable spreadsheet comprised of your issues, pull requests, and draft issues with metadata from {% data variables.product.company_short %} and the custom fields you've added to your project. You can group, sort, and filter items, and show or hide fields in your table layouts to suit the needs of everyone on your team.
The table layout is a powerful and adaptable spreadsheet comprised of your issues, pull requests, and draft issues with metadata from {% data variables.product.company_short %} and the custom fields you've added to your project. You can group, sort, and filter items, and show or hide fields in your table layouts to suit the needs of everyone on your team.

4
data/reusables/projects/create-issue-modal.md
View File

@@ -10,9 +10,9 @@
1. Below the repository dropdown, type a title for the new issue.
1. Optionally, use the fields below the title field to set assignees, labels, and milestones, and add the new issue to other projects.
1. Optionally, use the fields below the title field to set assignees, labels, and milestones, and add the new issue to other projects.
1. Optionally, type a description for your issue.
1. Optionally, type a description for your issue.
1. Optionally, if you want to create more issues, select **Create more** and the dialog will reopen when you create your issue.

6
data/reusables/projects/enable-basic-workflow.md
View File

@@ -3,9 +3,9 @@
{% data reusables.projects.access-workflows %}
1. Under "Default workflows", click on the workflow that you want to edit.
1. In the top right, click **Edit**.
![Screenshot showing a project's menu bar. The "Edit" button is highlighted with an orange rectangle.](/assets/images/help/projects-v2/workflow-start-editing.png)
1. Select whether the workflow should apply to issues, pull requests, or both.
1. Under "Set value", choose the value that you want to set the status to.
1. To save your changes and enable the workflow, click **Save and turn on workflow**.
@@ -16,6 +16,6 @@
1. Under "Default workflows", click on the workflow that you want to edit.
1. Select whether the workflow should apply to issues, pull requests, or both.
1. Next to "Set", choose the value that you want to set the status to.
1. If the workflow is disabled, click the toggle next to "Off" to enable the workflow.
1. If the workflow is disabled, click the toggle next to "Off" to enable the workflow.
{% endif %}

2
data/reusables/projects/graphql-ghes.md
View File

@@ -2,7 +2,7 @@
{% note %}
**Note:** The ProjectsV2 GraphQL API may not be available on {% data variables.location.product_location %}.
**Note:** The ProjectsV2 GraphQL API may not be available on {% data variables.location.product_location %}.
{% endnote %}

2
data/reusables/projects/projects-api.md
View File

@@ -1,7 +1,7 @@
{% ifversion fpt or ghec %}
{% note %}
**Notes:**
**Notes:**
- These endpoints only interact with {% data variables.product.prodname_projects_v1 %}. To manage {% data variables.product.prodname_projects_v2 %}, use the GraphQL API. For more information, see "[AUTOTITLE](/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects)."
- To create a new {% data variables.projects.projects_v1_board %}, the organization, user, or repository must already have at least one {% data variables.projects.projects_v1_board %}.

4
data/reusables/pull_requests/rebase_and_merge_verification.md
View File

@@ -1,5 +1,5 @@
When using the **Rebase and Merge** option on a pull request, it's important to note that the commits in the head branch are added to the base branch without commit signature verification.
When you use this option, {% data variables.product.prodname_dotcom %} creates a modified commit, using the data and content of the original commit. This means that {% data variables.product.prodname_dotcom %} didn't truly create this commit, and can't therefore sign it as a generic system user.
When using the **Rebase and Merge** option on a pull request, it's important to note that the commits in the head branch are added to the base branch without commit signature verification.
When you use this option, {% data variables.product.prodname_dotcom %} creates a modified commit, using the data and content of the original commit. This means that {% data variables.product.prodname_dotcom %} didn't truly create this commit, and can't therefore sign it as a generic system user.
{% data variables.product.prodname_dotcom %} doesn't have access to the committer's private signing keys, so it can't sign the commit on the user's behalf.
A workaround for this is to rebase and merge locally, and then push the changes to the pull request's base branch.

2
data/reusables/reminders/scheduled-reminders-limitations.md
View File

@@ -1 +1 @@
{% data variables.product.product_name %} will only trigger reminders for up to five repositories per owner and 20 pull requests per repository. Reminders are not sent when changes are merged from upstream into a fork.
{% data variables.product.product_name %} will only trigger reminders for up to five repositories per owner and 20 pull requests per repository. Reminders are not sent when changes are merged from upstream into a fork.

2
data/reusables/repositories/create-ruleset-step.md
View File

@@ -1,5 +1,5 @@
1. You can create a ruleset targeting branches, or a ruleset targeting tags.
- To create a ruleset targeting branches, click **New branch ruleset**.
- To create a ruleset targeting tags, select {% octicon "triangle-down" aria-label="Open ruleset creation menu" %}, then click **New tag ruleset**.
![Screenshot of the "Rulesets" page. Next to the "New branch ruleset" button, a dropdown menu is expanded, with an option labeled "New tag ruleset" outlined in orange.](/assets/images/help/repository/new-tag-ruleset.png)

2
data/reusables/repositories/fork-definition-long.md
View File

@@ -1 +1 @@
A fork is a new repository that shares code and visibility settings with the original “upstream” repository. Forks are often used to iterate on ideas or changes before they are proposed back to the upstream repository, such as in open source projects or when a user does not have write access to the upstream repository.
A fork is a new repository that shares code and visibility settings with the original “upstream” repository. Forks are often used to iterate on ideas or changes before they are proposed back to the upstream repository, such as in open source projects or when a user does not have write access to the upstream repository.

2
data/reusables/repositories/github-security-lab.md
View File

@@ -1 +1 @@
You can also join [{% data variables.product.prodname_security %}]({% data variables.product.prodname_security_link %}) to browse security-related topics and contribute to security tools and projects.
You can also join [{% data variables.product.prodname_security %}]({% data variables.product.prodname_security_link %}) to browse security-related topics and contribute to security tools and projects.

Some files were not shown because too many files have changed in this diff Show More