jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-19 09:57:42 -05:00
Code Issues Projects Releases Wiki Activity

Delete orphaned files (2024-11-04-16-33) (#52970)

Browse Source
This commit is contained in:
docs-bot
2024-11-05 09:46:11 -05:00
committed by GitHub
parent 7b2184d36e
commit 5ecbc6f0b2
207 changed files with 0 additions and 866 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
data/reusables/actions/action-labeler.md
View File

@@ -1 +0,0 @@
actions/labeler@v4

15
data/reusables/actions/actions-audit-events-for-enterprise.md
View File

@@ -1,15 +0,0 @@
| Action | Description |
|------------------|-------------------|
| `remove_self_hosted_runner` | Triggered when a self-hosted runner is removed. |
| `register_self_hosted_runner` | Triggered when a new self-hosted runner is registered. For more information, see "[AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/adding-self-hosted-runners)." |
| `runner_group_created` | Triggered when a self-hosted runner group is created. For more information, see "[AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/managing-access-to-self-hosted-runners-using-groups#about-self-hosted-runner-groups)." |
| `runner_group_removed` | Triggered when a self-hosted runner group is removed. For more information, see "[AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)." |
| `runner_group_runner_removed` | Triggered when the REST API is used to remove a self-hosted runner from a group. |
| `runner_group_runners_added` | Triggered when a self-hosted runner is added to a group. For more information, see "[AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)." |
| `runner_group_runners_updated` | Triggered when a runner group's list of members is updated. For more information, see "[AUTOTITLE](/rest/actions#set-self-hosted-runners-in-a-group-for-an-organization)." |
| `runner_group_updated` | Triggered when the configuration of a self-hosted runner group is changed. For more information, see "[AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)." |
| `self_hosted_runner_updated` | Triggered when the runner application is updated. Can be viewed using the REST API and the UI; not visible in the JSON/CSV export. For more information, see "[AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/about-self-hosted-runners#about-self-hosted-runners)." |
| {% ifversion fpt or ghec %} |
| `self_hosted_runner_online` | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." |
| `self_hosted_runner_offline` | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." |
| {% endif %} |

12
data/reusables/actions/actions-audit-events-workflow.md
View File

@@ -1,12 +0,0 @@
| Action | Description
|------------------|-------------------
| `cancel_workflow_run` | Triggered when a workflow run has been cancelled. For more information, see "[AUTOTITLE](/actions/managing-workflow-runs/canceling-a-workflow)."
| `completed_workflow_run` | Triggered when a workflow status changes to `completed`. Can only be viewed using the REST API; not visible in the UI or the JSON/CSV export. For more information, see "[AUTOTITLE](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)."
| `created_workflow_run` | Triggered when a workflow run is created. Can only be viewed using the REST API; not visible in the UI or the JSON/CSV export. For more information, see "[AUTOTITLE](/actions/learn-github-actions/understanding-github-actions#create-an-example-workflow)."
| `delete_workflow_run` | Triggered when a workflow run is deleted. For more information, see "[AUTOTITLE](/actions/managing-workflow-runs/deleting-a-workflow-run)."
| `disable_workflow` | Triggered when a workflow is disabled.
| `enable_workflow` | Triggered when a workflow is enabled, after previously being disabled by `disable_workflow`.
| `rerun_workflow_run` | Triggered when a workflow run is re-run. For more information, see "[AUTOTITLE](/actions/managing-workflow-runs/re-running-workflows-and-jobs)."
| `prepared_workflow_job` | Triggered when a workflow job is started. Includes the list of secrets that were provided to the job. Can only be viewed using the REST API. It is not visible in the {% data variables.product.prodname_dotcom %} web interface or included in the JSON/CSV export. For more information, see "[AUTOTITLE](/actions/using-workflows/events-that-trigger-workflows)."
| `approve_workflow_job` | Triggered when a workflow job has been approved. For more information, see "[AUTOTITLE](/actions/managing-workflow-runs/reviewing-deployments)."
| `reject_workflow_job` | Triggered when a workflow job has been rejected. For more information, see "[AUTOTITLE](/actions/managing-workflow-runs/reviewing-deployments)."

5
data/reusables/actions/cache-no-org-policy.md
View File

@@ -1,5 +0,0 @@
{% note %}
**Note:** Unlike other {% data variables.product.prodname_actions %} policy settings, there is no organization-level policy for setting the {% data variables.product.prodname_actions %} cache size. The enterprise policy is applied directly to repositories.
{% endnote %}

5
data/reusables/actions/caching-availability.md
View File

@@ -1,5 +0,0 @@
{% ifversion ghes %}
{% data variables.product.prodname_actions %} caching is only available for repositories hosted on {% data variables.product.prodname_ghe_server %} 3.5 and later. For more information, see "[Caching dependencies to speed up workflows](/actions/guides/caching-dependencies-to-speed-up-workflows)."
{% endif %}

1
data/reusables/actions/checkout-action-table-entry.md
View File

@@ -1 +0,0 @@
| Cloning your repository to the runner | [`actions/checkout`](https://github.com/actions/checkout)|

1
data/reusables/actions/concurrency-table-entry.md
View File

@@ -1 +0,0 @@
| Controlling how many workflow runs or jobs can run at the same time | [`concurrency`](/actions/using-jobs/using-concurrency)|

9
data/reusables/actions/configure-runner-group-access.md
View File

@@ -1,9 +0,0 @@
{% warning %}
**Warning**
{% data reusables.actions.self-hosted-runner-security %}
For more information, see "[AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)."
{% endwarning %}

1
data/reusables/actions/cron-table-entry.md
View File

@@ -1 +0,0 @@
| Running a workflow at regular intervals | [`schedule`](/actions/using-workflows/events-that-trigger-workflows#schedule) |

5
data/reusables/actions/deployment-history-beta-note.md
View File

@@ -1,5 +0,0 @@
{% note %}
**Note:** Deployment history is currently in {% data variables.release-phases.public_preview %} and subject to change.
{% endnote %}

1
data/reusables/actions/example-diagram-intro.md
View File

@@ -1 +0,0 @@
The following diagram shows a high level view of the workflow's steps and how they run within the job:

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

@@ -1 +0,0 @@
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

1
data/reusables/actions/example-explanation-table-intro.md
View File

@@ -1 +0,0 @@
The following table explains how each of these features are used when creating a {% data variables.product.prodname_actions %} workflow.

8
data/reusables/actions/example-github-runner-comment.md
View File

@@ -1,8 +0,0 @@
# <!-- This is a YAML comment for use in annotated code examples. -->
# You can run this workflow using a different operating systems.
#
# The workflow template configures jobs to run on Linux, using the {% data variables.product.prodname_dotcom %}-hosted `ubuntu-latest` runners. You can change the `runs-on` key to run your jobs on a different operating system.
#
# For example, you can use the {% data variables.product.prodname_dotcom %}-hosted Windows runners by specifying `runs-on: windows-latest`. Or, you can run on the {% data variables.product.prodname_dotcom %}-hosted macOS runners using `runs-on: macos-latest`.
#
# You can also run jobs in Docker containers, or you can provide a self-hosted runner that runs on your own infrastructure. For more information, see "[AUTOTITLE](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idruns-on)."

1
data/reusables/actions/example-table-intro.md
View File

@@ -1 +0,0 @@
The example workflow demonstrates the following capabilities of {% data variables.product.prodname_actions %}.

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

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

1
data/reusables/actions/explanation-name-key.md
View File

@@ -1 +0,0 @@
This defines the name of the workflow as it will appear in the "Actions" tab of the {% data variables.product.prodname_dotcom %} repository.

8
data/reusables/actions/hardware-requirements-3.4.md
View File

@@ -1,8 +0,0 @@
| vCPUs | Memory | Maximum Concurrency |
| :---| :--- | :--- |
| 8 | 64 GB | 300 jobs |
| 16 | 128 GB | 700 jobs |
| 32 | 160 GB | 1500 jobs |
| 64 | 256 GB | 2500 jobs |
| 96 | 384 GB | 4500 jobs |
| 128 | 550 GB | 5000 jobs |

7
data/reusables/actions/hardware-requirements-3.5.md
View File

@@ -1,7 +0,0 @@
| vCPUs | Memory | Maximum Concurrency |
| :---| :--- | :--- |
| 8 | 64 GB | 740 jobs |
| 16 | 128 GB | 1250 jobs |
| 32 | 160 GB | 2700 jobs |
| 64 | 256 GB | 4500 jobs |
| 96 | 384 GB | 7000 jobs |

1
data/reusables/actions/if-conditions-table-entry.md
View File

@@ -1 +0,0 @@
| Preventing a job from running unless specific conditions are met | [`if`](/actions/using-jobs/using-conditions-to-control-job-execution)|

154
data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md
View File

@@ -1,154 +0,0 @@
Use `jobs.<job_id>.runs-on` to define the type of machine to run the job on.
{% ifversion fpt or ghec %}- The destination machine can be either a [{% data variables.product.prodname_dotcom %}-hosted runner](#choosing-github-hosted-runners), [{% data variables.actions.hosted_runner %}](#choosing-runners-in-a-group), or a [self-hosted runner](#choosing-self-hosted-runners).{% else %}
* The destination machine can be a [self-hosted runner](#choosing-self-hosted-runners).{% endif %}
{% ifversion target-runner-groups %}- You can target runners based on the labels assigned to them, or their group membership, or a combination of these.{% else %}
* You can target runners based on the labels assigned to them.{% endif %}
* You can provide `runs-on` as:
* A single string
* A single variable containing a string
* An array of strings, variables containing strings, or a combination of both
* A `key: value` pair using the `group` or `labels` keys
* If you specify an array of strings or variables, your workflow will execute on any runner that matches all of the specified `runs-on` values. For example, here the job will only run on a self-hosted runner that has the labels `linux`, `x64`, and `gpu`:
```yaml
runs-on: [self-hosted, linux, x64, gpu]
```
For more information, see "[Choosing self-hosted runners](#choosing-self-hosted-runners)."
* You can mix strings and variables in an array. For example:
{% raw %}
```yaml
on:
workflow_dispatch:
inputs:
chosen-os:
required: true
type: choice
options:
- Ubuntu
- macOS
jobs:
test:
runs-on: [self-hosted, "${{ inputs.chosen-os }}"]
steps:
- run: echo Hello world!
```
{% endraw %}
* If you would like to run your workflow on multiple machines, use [`jobs.<job_id>.strategy`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstrategy).
{% note %}
**Note:** Quotation marks are not required around simple strings like `self-hosted`, but they are required for expressions like {% raw %} `"${{ inputs.chosen-os }}"`{% endraw %}.
{% endnote %}
{% data reusables.actions.enterprise-github-hosted-runners %}
### Choosing {% data variables.product.prodname_dotcom %}-hosted runners
If you use a {% data variables.product.prodname_dotcom %}-hosted runner, each job runs in a fresh instance of a runner image specified by `runs-on`.
Available {% data variables.product.prodname_dotcom %}-hosted runner labels are:
<table style="width:100%">
<thead>
<tr>
<th scope="col"><b>OS (YAML workflow label)</b></th>
<th scope="col"><b>Notes</b></th>
</tr>
</thead>
<tbody>
<tr>
<td>
<code>ubuntu-latest</code>,<code>ubuntu-24.04</code>, <code>ubuntu-22.04</code>, <code>ubuntu-20.04</code>
</td>
<td>
The <code>ubuntu-latest</code> label currently uses the Ubuntu 24.04 runner image.
</td>
</tr>
<tr>
<td>
<code>windows-latest</code>, <code>windows-2022</code>, <code>windows-2019</code>
</td>
<td>
The <code>windows-latest</code> label currently uses the Windows 2022 runner image.
</td>
</tr>
<tr>
<td>
<code>macos-latest</code>, <code>macos-15</code> [{% data variables.release-phases.public_preview_caps %}], <code>macos-14</code>, <code>macos-13</code>, <code>macos-12</code>
</td>
<td>
The <code>macos-latest</code> workflow label currently uses the macOS 14 runner image.
</td>
</tr>
</tbody>
</table>
For more information about {% data variables.product.prodname_dotcom %}-hosted runner specifications, see "[AUTOTITLE](/actions/using-github-hosted-runners/about-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources)."
{% note %}
**Note:** The `-latest` runner images are the latest stable images that {% data variables.product.prodname_dotcom %} provides, and might not be the most recent version of the operating system available from the operating system vendor.
{% endnote %}
{% warning %}
**Warning:** Beta and Deprecated Images are provided "as-is", "with all faults" and "as available" and are excluded from the service level agreement and warranty. Beta Images may not be covered by customer support.
{% endwarning %}
#### Example: Specifying an operating system
```yaml
runs-on: ubuntu-latest
```
For more information, see "[AUTOTITLE](/actions/using-github-hosted-runners/about-github-hosted-runners)."
### Choosing self-hosted runners
{% data reusables.actions.self-hosted-runner-labels-runs-on %}
#### Example: Using labels for runner selection
```yaml
runs-on: [self-hosted, linux]
```
For more information, see "[AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/about-self-hosted-runners)" and "[AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/using-self-hosted-runners-in-a-workflow)."
{% ifversion target-runner-groups %}
### Choosing runners in a group
You can use `runs-on` to target runner groups, so that the job will execute on any runner that is a member of that group. For more granular control, you can also combine runner groups with labels.
{% ifversion fpt or ghec %}
Runner groups can only have [{% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/using-larger-runners/about-larger-runners) or [self-hosted runners](/actions/hosting-your-own-runners) as members.
{% endif %}
#### Example: Using groups to control where jobs are run
{% data reusables.actions.jobs.example-runs-on-groups %}
#### Example: Combining groups and labels
{% data reusables.actions.jobs.example-runs-on-labels-and-groups %}
{% ifversion ghec or ghes %}
#### Example: using prefixes to differentiate runner groups
{% data reusables.actions.using-prefixes-to-differentiate-runner-groups %}
{% endif %}
{% endif %}

4
data/reusables/actions/learning-actions.md
View File

@@ -1,4 +0,0 @@
* To learn about {% data variables.product.prodname_actions %} concepts, see "[AUTOTITLE](/actions/learn-github-actions/understanding-github-actions)."
* For more step-by-step guide for creating a basic workflow, see "[AUTOTITLE](/actions/quickstart)."
* If you're comfortable with the basics of {% data variables.product.prodname_actions %}, you can learn about workflows and their features at "[AUTOTITLE](/actions/using-workflows/about-workflows)."

1
data/reusables/actions/permissions-table-entry.md
View File

@@ -1 +0,0 @@
| Setting permissions for the token | [`permissions`](/actions/using-jobs/assigning-permissions-to-jobs)|

1
data/reusables/actions/pull-request-table-entry.md
View File

@@ -1 +0,0 @@
| Triggering a workflow to run automatically | [`pull_request`](/actions/using-workflows/events-that-trigger-workflows#pull_request) |

1
data/reusables/actions/push-table-entry.md
View File

@@ -1 +0,0 @@
| Triggering a workflow to run automatically | [`push`](/actions/using-workflows/events-that-trigger-workflows#push) |

1
data/reusables/actions/secrets-table-entry.md
View File

@@ -1 +0,0 @@
| Referencing secrets in a workflow | [Secrets](/actions/security-guides/using-secrets-in-github-actions)|

20
data/reusables/actions/self-hosted-runner-navigate-to-org-enterprise.md
View File

@@ -1,20 +0,0 @@
{% ifversion fpt %}
1. Navigate to the main page of the organization where your self-hosted runner is registered.
1. Click {% octicon "gear" aria-label="The Settings gear" %} **Settings**.
{% data reusables.organizations.settings-sidebar-actions-runners %}
{% elsif ghec or ghes %}
1. Navigate to where your runner is registered:
* **In an organization**: navigate to the main page and click {% octicon "gear" aria-label="The Settings gear" %} **Settings**.
* **If using an enterprise-level runner**:
{% indented_data_reference reusables.enterprise-accounts.access-enterprise spaces=5 %}
1. Navigate to the {% data variables.product.prodname_actions %} settings:
* **In an organization**:
{% indented_data_reference reusables.actions.settings-ui.settings-actions-runners spaces=5 %}
* **If using an enterprise-level runner**:
{% indented_data_reference reusables.enterprise-accounts.policies-tab spaces=5 %}
{% indented_data_reference reusables.enterprise-accounts.actions-tab spaces=5 %}
{% indented_data_reference reusables.enterprise-accounts.actions-runners-tab spaces=5 %}
{% endif %}

1
data/reusables/actions/self-hosted-runners-software.md
View File

@@ -1 +0,0 @@
You must install the required software on your self-hosted runners. For more information about self-hosted runners, see "[AUTOTITLE](/actions/hosting-your-own-runners)."

1
data/reusables/actions/setup-node-table-entry.md
View File

@@ -1 +0,0 @@
| Installing `node` on the runner | [`actions/setup-node`](https://github.com/actions/setup-node) |

1
data/reusables/actions/workflow-dispatch-table-entry.md
View File

@@ -1 +0,0 @@
| Manually running a workflow from the UI | [`workflow_dispatch`](/actions/using-workflows/events-that-trigger-workflows#workflow_dispatch)|

1
data/reusables/actions/workflows/setup-java-step-explainer.md
View File

@@ -1 +0,0 @@
# This step uses the `actions/setup-java` action to configure the Eclipse Temurin (Java) 17 JDK by Eclipse Adoptium.

1
data/reusables/actions/workflows/starter-workflows.md
View File

@@ -1 +0,0 @@
The default workflow templates are excellent starting points when creating your build and test workflow, and you can customize the workflow template to suit your project’s needs.

1
data/reusables/actions/workflows/workflow-checkout-step-explainer.md
View File

@@ -1 +0,0 @@
# This step uses the `actions/checkout` action to download a copy of your repository on the runner.

1
data/reusables/advanced-security/more-info-ghas-secret-scanning.md
View File

@@ -1 +0,0 @@
For more information, see {% ifversion fpt or ghec %}"[AUTOTITLE](/code-security/secret-scanning/managing-alerts-from-secret-scanning/about-alerts#about-user-alerts)"{% elsif ghes %}"[AUTOTITLE](/code-security/secret-scanning/managing-alerts-from-secret-scanning/about-alerts#about-secret-scanning-alerts)"{% endif %} and "[AUTOTITLE](/get-started/learning-about-github/about-github-advanced-security)."

1
data/reusables/advanced-security/more-information-about-enforcement-policy.md
View File

@@ -1 +0,0 @@
For more information, see "[Enforcing policies for {% data variables.product.prodname_advanced_security %} in your enterprise]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)."

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

@@ -1,8 +0,0 @@
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)
1. Optionally, click **Automatically enable for repositories added to {% data variables.product.prodname_secret_scanning %}**.{% ifversion secret-scanning-custom-link-on-block %}
1. Optionally, to include a custom link in the message that members will see when they attempt to push a secret, click **Add a resource link in the CLI and web UI when a commit is blocked**, then type a URL, and click **Save link**.
![Screenshot of the "Push protection" section of the "Code security and analysis" page. The "Add a resource link in the CLI and web UI when a commit is blocked" checkbox and the custom link text field are highlighted with a dark orange outline.](/assets/images/help/organizations/secret-scanning-custom-link.png){% endif %}

5
data/reusables/advanced-security/secret-scanning-push-protection-org.md
View File

@@ -1,5 +0,0 @@
1. Under "{% data variables.product.prodname_secret_scanning_caps %}", under "Push protection", click **Enable all**.
1. Optionally, click **Automatically enable for repositories added to {% data variables.product.prodname_secret_scanning %}**.{% ifversion push-protection-custom-link-orgs %}
1. Optionally, to include a custom link in the message that members will see when they attempt to push a secret, select **Add a resource link in the CLI and web UI when a commit is blocked**, then type a URL, and click **Save link**.
![Screenshot of the "Push protection" section of the "Code security and analysis" page. The "Add a resource link in the CLI and web UI when a commit is blocked" checkbox and the custom link text field are highlighted with a dark orange outline.](/assets/images/help/organizations/secret-scanning-custom-link.png){% endif %}

5
data/reusables/advisory-database/beta-malware-advisories.md
View File

@@ -1,5 +0,0 @@
{% note %}
**Note:** Advisories for malware are currently in {% data variables.release-phases.public_preview %} and subject to change.
{% endnote %}

1
data/reusables/apps/user-to-server-rate-limits.md
View File

@@ -1 +0,0 @@
{% ifversion ghes %}By default, user access token{% else %}User access token{% endif %} requests are limited to 5,000 requests per hour and per authenticated user. All requests from {% data variables.product.prodname_oauth_apps %} authorized by a user or a {% data variables.product.pat_generic %} owned by the user, and requests authenticated with any of the user's authentication credentials, share the same quota of 5,000 requests per hour for that user.

12
data/reusables/audit_log/audit-log-events-workflows.md
View File

@@ -1,12 +0,0 @@
| Action | Description
|--------|------------
| `workflows.approve_workflow_job` | A workflow job was approved. For more information, see "[AUTOTITLE](/actions/managing-workflow-runs/reviewing-deployments)."
| `workflows.cancel_workflow_run` | A workflow run was cancelled. For more information, see "[AUTOTITLE](/actions/managing-workflow-runs/canceling-a-workflow)."
| `workflows.delete_workflow_run` | A workflow run was deleted. For more information, see "[AUTOTITLE](/actions/managing-workflow-runs/deleting-a-workflow-run)."
| `workflows.disable_workflow` | A workflow was disabled.
| `workflows.enable_workflow` | A workflow was enabled, after previously being disabled by `disable_workflow`.
| `workflows.reject_workflow_job` | A workflow job was rejected. For more information, see "[AUTOTITLE](/actions/managing-workflow-runs/reviewing-deployments)."
| `workflows.rerun_workflow_run` | A workflow run was re-run. For more information, see "[AUTOTITLE](/actions/managing-workflow-runs/re-running-workflows-and-jobs)."
| `workflows.completed_workflow_run` | A workflow status changed to `completed`. Can only be viewed using the REST API; not visible in the UI or the JSON/CSV export. For more information, see "[AUTOTITLE](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)."
| `workflows.created_workflow_run` | A workflow run was created. Can only be viewed using the REST API; not visible in the UI or the JSON/CSV export. For more information, see "[AUTOTITLE](/actions/learn-github-actions/understanding-github-actions#create-an-example-workflow)."
| `workflows.prepared_workflow_job` | A workflow job was started. Includes the list of secrets that were provided to the job. Can only be viewed using the REST API. It is not visible in the {% data variables.product.prodname_dotcom %} web interface or included in the JSON/CSV export. For more information, see "[AUTOTITLE](/actions/using-workflows/events-that-trigger-workflows)."

1
data/reusables/code-scanning/autobuild-compiled-languages.md
View File

@@ -1 +0,0 @@
If you enable default setup, the `autobuild` build mode will be used to build compiled languages, as part of your automatically configured {% data variables.code-scanning.codeql_workflow %}. If you enable advanced setup, the basic {% data variables.code-scanning.codeql_workflow %} uses the `autobuild` build mode. Alternatively, you can change the build mode for your compiled languages to `manual` and instead specify explicit build commands to analyze only the files that are built by these custom commands.

1
data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md
View File

@@ -1 +0,0 @@
You can run {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} within {% data variables.product.product_name %} using {% data variables.product.prodname_actions %}. Alternatively, if you use a third-party continuous integration or continuous delivery/deployment (CI/CD) system, you can run {% data variables.product.prodname_codeql %} analysis in your existing system and upload the results to {% data variables.product.github %}.

1
data/reusables/code-scanning/default-setup-info-link.md
View File

@@ -1 +0,0 @@
For information about eligible repositories, see "[AUTOTITLE](/code-security/code-scanning/enabling-code-scanning/configuring-default-setup-for-code-scanning-at-scale#eligible-repositories-default-setup)."

1
data/reusables/code-scanning/edit-workflow.md
View File

@@ -1 +0,0 @@
Typically, you don't need to edit the generated workflow file for {% data variables.product.prodname_code_scanning %}. However, if required, you can edit the workflow to customize some of the settings. For example, you can edit {% data variables.product.prodname_dotcom %}'s {% data variables.code-scanning.codeql_workflow %} to specify the frequency of scans, the languages or directories to scan, and what {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} looks for in your code. You might also need to edit the {% data variables.code-scanning.codeql_workflow %} if you use a specific set of commands to compile your code.

0
data/reusables/code-scanning/sarif-category.md
View File

6
data/reusables/codeql-cli/download-info-macos-catalina-or-newer.md
View File

@@ -1,6 +0,0 @@
From macOS version 10.15 ("Catalina") onwards you need to ensure that your web browser does not automatically extract zip files. If you use Safari, complete the following steps before downloading the {% data variables.product.prodname_codeql_cli %} zip archive:
1. Open Safari.
1. From the Safari menu, select **Preferences...** or **Settings...** (version 13 "Ventura" onwards).
1. Click the **General** Tab.
1. Ensure the check-box labeled **Open "safe" files after downloading** is unchecked.

6
data/reusables/codeql-cli/extraction-info-macos-catalina-or-newer.md
View File

@@ -1,6 +0,0 @@
macOS "Catalina", "Big Sur", "Monterey", or "Ventura" users should run the following commands in the Terminal, where `${extraction-root}` is the path to the directory where you will extract the {% data variables.product.prodname_codeql_cli %} zip archive:
1. `mv ~/Downloads/codeql\*.zip ${extraction-root}`
1. `cd ${extraction-root}`
1. `/usr/bin/xattr -c codeql\*.zip`
1. `unzip codeql\*.zip`

1
data/reusables/copilot/about-copilot.md
View File

@@ -1 +0,0 @@
{% data variables.product.prodname_copilot %} is an AI-powered coding assistant that helps developers write code faster.

20
data/reusables/copilot/chat-asking-questions.md
View File

@@ -1,20 +0,0 @@
1. To ask a question about the code that's currently visible in the editor, type `#editor` followed by your question.
For example, you could type `#editor what does this code do?` to ask {% data variables.product.prodname_copilot_chat_short %} for a description of the code's purpose.
Use the `#editor` command, anywhere in your question, to tell {% data variables.product.prodname_copilot_chat_short %} to focus on the code that's currently visible in the editor.
1. If a single method is visible in full in the editor, you could ask {% data variables.product.prodname_copilot_chat_short %} to generate a unit test for the method by typing `Write a unit test for the method in the #editor`.
Alternatively, select the code you want to generate a unit test for, then ask {% data variables.product.prodname_copilot_short %}: `#selection write a unit test for this code`.
The `#selection` command ensure that {% data variables.product.prodname_copilot_short %} focuses on the selected code when responding to a question.
1. To fix a bug in some code, select the code in the editor, then ask {% data variables.product.prodname_copilot_short %}: `#selection fix the bug in this code`.
1. To focus {% data variables.product.prodname_copilot_short %} on one or more specific files when you ask a question, use the `#file` command.
1. In the {% data variables.product.prodname_copilot_chat_short %} window, type `#file` and press <kbd>Enter</kbd>. This opens the Quick Open palette at the top of the editor.
1. Select from the list of recently opened files, or search for the file you want to focus on and select it.
1. Type your question. For example, `#file:app.js What does this file do?`.
You can use the `#file` command multiple times in your question to focus {% data variables.product.prodname_copilot_short %} on more than one file.

1
data/reusables/copilot/chat-beta-indexing.md
View File

@@ -1 +0,0 @@
Only selected repositories have been semantically indexed for this {% data variables.release-phases.public_preview %}. The ability for you to index your own repositories will be added soon.

1
data/reusables/copilot/chat-open-visualstudio.md
View File

@@ -1 +0,0 @@
1. In the {% data variables.product.prodname_vs %} menu bar, to launch {% data variables.product.prodname_copilot_chat_short %}, click **View**, then click **{% data variables.product.prodname_copilot_chat %}**.

1
data/reusables/copilot/chat-procedural-intro.md
View File

@@ -1 +0,0 @@
{% data variables.product.prodname_copilot_chat %} is a chat interface that lets you ask and receive answers to coding-related questions directly within a supported IDE. {% data variables.product.prodname_copilot_chat_short %} can help you with a variety of coding-related tasks, like offering you code suggestions, providing natural language descriptions of a piece of code's functionality and purpose, generating unit tests for your code, and proposing fixes for bugs in your code. For more information, see "[AUTOTITLE](/copilot/github-copilot-chat/copilot-chat-in-ides/about-github-copilot-chat-in-your-ide) and "[AUTOTITLE](/enterprise-cloud@latest/copilot/github-copilot-chat/copilot-chat-in-github/using-github-copilot-chat-in-githubcom)."

1
data/reusables/copilot/chat-subscription-prerequisite.md
View File

@@ -1 +0,0 @@
* To use {% data variables.product.prodname_copilot_chat %} you must have an active {% data variables.product.prodname_copilot %} subscription. For more information, see "[AUTOTITLE](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot)."

1
data/reusables/copilot/click-copilot-icon.md
View File

@@ -1 +0,0 @@
1. On any page on {% data variables.product.github %}, click the **{% octicon "copilot" aria-hidden="true" %}** {% data variables.product.prodname_copilot %} icon at the top right of the page.

1
data/reusables/copilot/code-examples-limitations.md
View File

@@ -1 +0,0 @@
> [!NOTE] If you have duplication detection enabled for {% data variables.product.prodname_copilot %}, you may receive limited suggestions, or no suggestions, when using the code examples provided. As an alternative, you can start by typing your own code to see suggestions from {% data variables.product.prodname_copilot %}. For more information on duplication detection, see "[AUTOTITLE](/copilot/configuring-github-copilot/configuring-your-personal-github-copilot-settings-on-githubcom#enabling-or-disabling-suggestions-matching-public-code)."

19
data/reusables/copilot/copilot-business-features.md
View File

@@ -1,19 +0,0 @@
## Administrative features for {% data variables.product.prodname_copilot_short %}
These features are available to organization owners and administrators to manage {% data variables.product.prodname_copilot %} in their organization.
### Content exclusion
Content exclusions allow you to configure {% data variables.product.prodname_copilot %} to ignore certain files in your repository. This can be useful if you have files that you don't want to be available to {% data variables.product.prodname_copilot %}. See "[AUTOTITLE](/copilot/managing-copilot/managing-github-copilot-in-your-organization/managing-github-copilot-features-in-your-organization/about-content-exclusions-for-github-copilot)."
### Managing access to {% data variables.product.prodname_copilot %}
Organization owners can manage access to {% data variables.product.prodname_copilot %} for their organization, and review usage data to inform their decision. For more information, see "[AUTOTITLE](/copilot/managing-github-copilot-in-your-organization/managing-access-for-copilot-business-in-your-organization)."
### Managing policies for {% data variables.product.prodname_copilot %}
Organization owners can manage policies for {% data variables.product.prodname_copilot %} in their organization. For more information, see "[AUTOTITLE](/copilot/managing-github-copilot-in-your-organization/managing-policies-for-copilot-business-in-your-organization)."
### Audit logs
Organization owners can review audit logs for {% data variables.product.prodname_copilot %} in their organization, to understand what actions have been taken and by which users. For more information, see "[AUTOTITLE](/copilot/managing-copilot/managing-github-copilot-in-your-organization/reviewing-github-copilot-activity-in-your-organization/reviewing-audit-logs-for-copilot-business)."

1
data/reusables/copilot/copilot-chat-exclusively-code-questions.md
View File

@@ -1 +0,0 @@
{% data variables.product.prodname_copilot_chat %} is intended to answer exclusively coding related questions that you ask in natural language. For example, you can ask {% data variables.product.prodname_copilot_chat %} to help you write a function that returns the sum of two numbers.

4
data/reusables/copilot/copilot-chat-mobile-enable.md
View File

@@ -1,4 +0,0 @@
{% data reusables.enterprise-accounts.policies-tab %}
{% data reusables.enterprise-accounts.copilot-tab %}
1. Click the **Policies** tab.
1. To the right of "{% data variables.product.prodname_copilot_mobile_short %}", select the dropdown menu, then choose the appropriate option. By default, {% data variables.product.prodname_copilot_mobile_short %} is disabled at the organization level.

1
data/reusables/copilot/copilot-cli-about.md
View File

@@ -1 +0,0 @@
{% data variables.product.prodname_copilot_cli %} is an extension for {% data variables.product.prodname_cli %} which provides a chat-like interface in the terminal that allows you to ask questions about commands you run from the command line.

8
data/reusables/copilot/copilot-cli-enable.md
View File

@@ -1,8 +0,0 @@
{% data reusables.enterprise-accounts.policies-tab %}
{% data reusables.enterprise-accounts.copilot-tab %}
1. Click the **Policies** tab.
1. To the right of "{% data variables.product.prodname_copilot_cli %}", select the dropdown menu, then choose the appropriate option.
* To allow each of your organizations to set their own policy, select **No policy**.
* To enable {% data variables.product.prodname_copilot_cli_short %} for all organizations under your enterprise, select **Enabled**.
* To disable {% data variables.product.prodname_copilot_cli_short %} for all organizations under your enterprise, select **Disabled**.

15
data/reusables/copilot/copilot-enterprise-enable.md
View File

@@ -1,15 +0,0 @@
{% data reusables.enterprise-accounts.policies-tab %}
{% data reusables.enterprise-accounts.copilot-tab %}
{% data reusables.enterprise-accounts.copilot-policies-tab %}
1. Next to "{% data variables.product.prodname_copilot_short %} in {% data variables.product.prodname_dotcom_the_website %}," click the dropdown menu and select the policy you want to enforce. By default, {% data variables.product.prodname_copilot_short %} in {% data variables.product.prodname_dotcom_the_website %} is disabled at the organization level.
1. Optionally, if you select **Enabled** for the "{% data variables.product.prodname_copilot_short %} in {% data variables.product.prodname_dotcom_the_website %}" policy, you can also choose to allow or disallow feedback on pull request summaries.
* To allow feedback after {% data variables.product.prodname_copilot_short %} generates a pull request summary, select **Opt in to user feedback collection**. Developers will be able to provide feedback after {% data variables.product.prodname_copilot_short %} generates a pull request summary, and the summary will be sent to {% data variables.product.prodname_dotcom %} for context.
* To disallow feedback after {% data variables.product.prodname_copilot_short %} generates a pull request summary, deselect **Opt in to user feedback collection**. Developers will still be able to provide feedback on {% data variables.product.prodname_copilot_short %} with the feedback icons attached to each {% data variables.product.prodname_copilot_chat_short %} response, and via the "Give feedback" link in conversations.
For more information about user feedback collection for {% data variables.product.prodname_copilot_short %}, see "[AUTOTITLE](/copilot/github-copilot-chat/copilot-chat-in-github/using-github-copilot-chat-in-githubcom#sharing-feedback-about-github-copilot-chat-in-githubcom)."
> [!NOTE] If you choose **No policy** for the "{% data variables.product.prodname_copilot_short %} in {% data variables.product.prodname_dotcom_the_website %}" option, and an organization owner enables "{% data variables.product.prodname_copilot_short %} in {% data variables.product.prodname_dotcom_the_website %}" in their organization, user feedback collection is enabled by default, and can be managed at the organization level.
1. Next to "Give {% data variables.product.prodname_copilot_short %} access to Bing," click the dropdown menu and select the policy you want to enforce. By default, Bing is disabled at the organization level.
> [!NOTE] Bing search integration into {% data variables.product.prodname_copilot_chat_dotcom_short %} is currently in {% data variables.release-phases.public_preview %} and is subject to change.

15
data/reusables/copilot/copilot-enterprise-features.md
View File

@@ -1,15 +0,0 @@
### {% data variables.product.prodname_copilot_chat_dotcom %}
{% data variables.product.prodname_copilot_chat_dotcom %} is a chat interface that lets you ask and receive answers to coding-related questions within {% data variables.product.github %}. For more information, see "[AUTOTITLE](/copilot/github-copilot-chat/copilot-chat-in-github/about-github-copilot-chat-in-githubcom)."
### {% data variables.product.prodname_copilot_for_prs %}
{% data variables.product.prodname_copilot_for_prs %} is an AI-powered feature that allows you to create a summary of the changes that were made in a pull request, which files they impact, and what a reviewer should focus on when they conduct their review. For more information, see "[AUTOTITLE](/copilot/github-copilot-enterprise/copilot-pull-request-summaries/about-copilot-pull-request-summaries)."
### {% data variables.product.prodname_copilot_autocomplete_pr %} (beta)
{% data variables.product.prodname_copilot_autocomplete_pr %} is a feature that provides AI-generated autocompletions to help you write pull request descriptions quickly and accurately. For more information, see "[AUTOTITLE](/copilot/using-github-copilot/using-copilot-pull-request-autocomplete)."
### {% data variables.product.prodname_copilot_short %} knowledge bases
Knowledge bases are collections of Markdown documentation from one or more repositories. When you ask {% data variables.product.prodname_copilot_chat_short %} a question in the {% data variables.product.github %} website, {% data variables.product.prodname_vscode_shortname %}, or {% data variables.product.prodname_vs %}, you can specify a knowledge base as the context for your question. For more information, see "[AUTOTITLE](/enterprise-cloud@latest/copilot/managing-copilot/managing-github-copilot-in-your-organization/managing-github-copilot-features-in-your-organization/managing-copilot-knowledge-bases)."

3
data/reusables/copilot/copilot-extensions/compatible-chat-interfaces.md
View File

@@ -1,3 +0,0 @@
* {% data variables.product.prodname_copilot_chat_short %} in {% data variables.product.prodname_vs %}
* {% data variables.product.prodname_copilot_chat_short %} in {% data variables.product.prodname_vscode %}
* {% data variables.product.prodname_copilot_chat_dotcom_short %}

5
data/reusables/copilot/copilot-individual-emus.md
View File

@@ -1,5 +0,0 @@
{% ifversion ghec %}
To sign up for {% data variables.product.prodname_copilot_for_individuals %}, you need a personal account on {% data variables.product.prodname_dotcom_the_website %}. To use {% data variables.product.prodname_copilot_short %} with a {% data variables.enterprise.prodname_managed_user %}, you must be granted access to a {% data variables.product.prodname_copilot_business_short %} or {% data variables.product.prodname_copilot_enterprise_short %} subscription. For more information, see "[AUTOTITLE](/copilot/about-github-copilot/what-is-github-copilot#getting-access-to-copilot)."
{% endif %}

15
data/reusables/copilot/copilot-individual-features.md
View File

@@ -1,15 +0,0 @@
### {% data variables.product.prodname_copilot %} in your IDE
{% data variables.product.prodname_copilot %} is an AI tool that offers autocomplete-style suggestions in your IDE. For more information, see "[AUTOTITLE](/copilot/using-github-copilot/getting-started-with-github-copilot)."
### {% data variables.product.prodname_copilot_mobile %}
{% data variables.product.prodname_copilot_mobile %} is a chat interface that lets you interact with {% data variables.product.prodname_copilot %}, to ask and receive answers to coding-related questions within {% data variables.product.prodname_mobile %}. For more information, see "[AUTOTITLE](/copilot/github-copilot-chat/copilot-chat-in-github-mobile/using-github-copilot-chat-in-github-mobile)."
### {% data variables.product.prodname_copilot_chat %} in your IDE
{% data variables.product.prodname_copilot_chat %} in your IDE is a chat interface that lets you ask and receive answers to coding-related questions within supported IDEs. For more information, see "[AUTOTITLE](/copilot/github-copilot-chat/copilot-chat-in-ides/using-github-copilot-chat-in-your-ide)."
### {% data variables.product.prodname_copilot_cli %}
{% data variables.product.prodname_copilot_cli %} provides a chat-like interface in the terminal that allows you to ask questions about the command line. You can ask {% data variables.product.prodname_copilot %} to provide either command suggestions or explanations of given commands. For more information, see "[AUTOTITLE](/copilot/github-copilot-in-the-cli/using-github-copilot-in-the-cli)."

1
data/reusables/copilot/create-c-file.md
View File

@@ -1 +0,0 @@
1. In {% data variables.product.prodname_vs %}, create a new C# (_*.cs_) file.

1
data/reusables/copilot/create-java-file.md
View File

@@ -1 +0,0 @@
1. In your JetBrains IDE, create a new Java (_*.java_) file.

1
data/reusables/copilot/create-sql-file.md
View File

@@ -1 +0,0 @@
1. In Azure Data Studio, create a new SQL file.

1
data/reusables/copilot/duplication-setting-org.md
View File

@@ -1 +0,0 @@
> [!NOTE] If you are a member of an organization on {% data variables.product.prodname_ghe_cloud %} who has been assigned a {% data variables.product.prodname_copilot %} seat through your organization, you will not be able to configure duplication detection in your personal account settings. Your duplication detection setting will be inherited from your organization or enterprise.

6
data/reusables/copilot/enabling-chat-enterprise.md
View File

@@ -1,6 +0,0 @@
{% data reusables.enterprise-accounts.policies-tab %}
{% data reusables.enterprise-accounts.copilot-tab %}
1. To the right of **{% data variables.product.prodname_copilot_chat %} {% data variables.release-phases.public_preview_caps %}**, select the dropdown menu, and then choose the appropriate option.
* Click **Allowed** to enable the {% data variables.product.prodname_copilot_chat %} {% data variables.release-phases.public_preview %} for all organizations under your enterprise.
* Click **Blocked** to disable the {% data variables.product.prodname_copilot_chat %} {% data variables.release-phases.public_preview %} for all organizations under your enterprise.
* Click **No policy** to allow each organization under your enterprise to set their own policy.

4
data/reusables/copilot/enabling-chat-organization.md
View File

@@ -1,4 +0,0 @@
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "copilot" aria-hidden="true" %} {% data variables.product.prodname_copilot_short %}**, and then click **Policies**.
1. To the right of **{% data variables.product.prodname_copilot_chat %} {% data variables.release-phases.public_preview_caps %}**, select the dropdown menu, and then click **Enabled** or **Disabled**.

23
data/reusables/copilot/enabling-copilot-chat-beta.md
View File

@@ -1,23 +0,0 @@
## Enabling or disabling {% data variables.product.prodname_copilot_chat %}
> [!NOTE] If you have a {% data variables.product.prodname_copilot_for_individuals %} subscription, you are automatically granted access to {% data variables.product.prodname_copilot_chat %}.
{% data variables.product.prodname_copilot_chat %} is available to all organizations and enterprises that have an active {% data variables.product.prodname_copilot_for_business %} license. You can enable or disable {% data variables.product.prodname_copilot_chat %} for your organization or enterprise in the {% data variables.product.prodname_copilot_for_business %} settings page.
If {% data variables.product.prodname_copilot_chat_short %} is enabled or disabled at the enterprise level, organizations within the enterprise cannot override the setting.
### Enabling or disabling {% data variables.product.prodname_copilot_chat %} at the organization level
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "copilot" aria-hidden="true" %} {% data variables.product.prodname_copilot_short %}**, and then click **Policies**.
1. To the right of **{% data variables.product.prodname_copilot_chat %} {% data variables.release-phases.public_preview_caps %}**, select the dropdown menu, and then click **Enabled** or **Disabled**.
### Enabling or disabling {% data variables.product.prodname_copilot_chat %} at the enterprise level
{% data reusables.enterprise-accounts.policies-tab %}
{% data reusables.enterprise-accounts.copilot-tab %}
1. To the right of **{% data variables.product.prodname_copilot_chat %} {% data variables.release-phases.public_preview_caps %}**, select the dropdown menu, and then choose the appropriate option.
* Click **Allowed** to enable the {% data variables.product.prodname_copilot_chat %} {% data variables.release-phases.public_preview %} for all organizations under your enterprise.
* Click **Blocked** to disable the {% data variables.product.prodname_copilot_chat %} {% data variables.release-phases.public_preview %} for all organizations under your enterprise.
* Click **No policy** to allow each organization under your enterprise to set their own policy.

1
data/reusables/copilot/enabling-github-copilot-for-business.md
View File

@@ -1 +0,0 @@
If you want to use {% data variables.product.prodname_copilot_for_business %} in your organization{% ifversion ghec %} or enterprise{% endif %}, you must first establish a policy for the use of {% data variables.product.prodname_copilot %}. Once {% data variables.product.prodname_copilot %} is enabled at the enterprise-level, you can configure {% data variables.product.prodname_copilot %} settings for each organization in your enterprise.

29
data/reusables/copilot/enabling-or-disabling-copilot.md
View File

@@ -1,29 +0,0 @@
> [!NOTE] If you have a {% data variables.product.prodname_copilot_for_individuals %} subscription, you are automatically granted access to {% data variables.product.prodname_copilot_chat %}.
{% data variables.product.prodname_copilot_chat %} is available to all organizations {% ifversion ghec %}and enterprises{% endif %} that have an active {% data variables.product.prodname_copilot_for_business %} {% ifversion ghec %}or {% data variables.product.prodname_copilot_enterprise %}{% endif %} subscription. You can enable or disable {% data variables.product.prodname_copilot_chat %} for your organization {% ifversion ghec %}or enterprise{% endif %} in the settings page for {% data variables.product.prodname_copilot_short %}.
{% ifversion ghec %}
If {% data variables.product.prodname_copilot_chat_short %} is enabled or disabled at the enterprise level, organizations within the enterprise cannot override the setting.
{% endif %}
### Enabling or disabling {% data variables.product.prodname_copilot_chat %} {% ifversion ghec %}at the organization level{% endif %}
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "copilot" aria-hidden="true" %} {% data variables.product.prodname_copilot_short %}**, and then click **Policies**.
1. To the right of **{% data variables.product.prodname_copilot_chat_short %} in the IDE**, select the dropdown menu, and then click **Enabled** or **Disabled**.
{% ifversion ghec %}
### Enabling or disabling {% data variables.product.prodname_copilot_chat %} at the enterprise level
{% data reusables.enterprise-accounts.policies-tab %}
{% data reusables.enterprise-accounts.copilot-tab %}
1. To the right of **{% data variables.product.prodname_copilot_chat_short %} in the IDE**, select the dropdown menu, and then choose the appropriate option.
* Click **Allowed** to enable {% data variables.product.prodname_copilot_chat %} for all organizations under your enterprise.
* Click **Blocked** to disable {% data variables.product.prodname_copilot_chat %} for all organizations under your enterprise.
* Click **No policy** to allow each organization under your enterprise to set their own policy.
{% endif %}

13
data/reusables/copilot/enabling-or-disabling-in-ads.md
View File

@@ -1,13 +0,0 @@
## Enabling or disabling {% data variables.product.prodname_copilot %}
You can enable or disable {% data variables.product.prodname_copilot %} from within Azure Data Studio. The {% data variables.product.prodname_copilot %} status icon in the bottom panel of the Azure Data Studio window indicates whether {% data variables.product.prodname_copilot %} is enabled or disabled. When enabled, the background color of the icon will match the color of the status bar. When disabled, the background color of the icon will contrast with the color of the status bar.
1. To enable or disable {% data variables.product.prodname_copilot %}, click the status icon in the bottom panel of the Azure Data Studio window.
![Screenshot of the bottom panel in Azure Data Studio. The {% data variables.product.prodname_copilot %} icon is outlined in dark orange.](/assets/images/help/copilot/status-icon-azure-data-studio.png)
1. If you are disabling {% data variables.product.prodname_copilot %}, you will be asked whether you want to disable suggestions globally, or for the language of the file you are currently editing.
* To disable suggestions from {% data variables.product.prodname_copilot %} globally, click **Disable Globally**.
* To disable suggestions from {% data variables.product.prodname_copilot %} for the specified language, click **Disable for LANGUAGE**.
![Screenshot of option to disable {% data variables.product.prodname_copilot %} globally or for the current language.](/assets/images/help/copilot/disable-copilot-global-or-language-ads.png)

1
data/reusables/copilot/enterprise-fpt-link.md
View File

@@ -1 +0,0 @@
> [!NOTE] You are currently viewing the documentation for Free, Pro, and Team plans. {% data variables.product.prodname_copilot_enterprise %} is only available to customers on the {% data variables.product.prodname_ghe_cloud %} plan. For full documentation of {% data variables.product.prodname_copilot_enterprise_short %}, see "[AUTOTITLE](/enterprise-cloud@latest/copilot/github-copilot-enterprise)." in the {% data variables.product.prodname_ghe_cloud %} documentation.

1
data/reusables/copilot/generating-suggestions-from-comments.md
View File

@@ -1 +0,0 @@
You can describe something you want to do using natural language within a comment, and {% data variables.product.prodname_copilot %} will suggest the code to accomplish your goal.

1
data/reusables/copilot/indexing-note.md
View File

@@ -1 +0,0 @@
> [!NOTE] Initial indexing can take up to 30 minutes for large repositories. Once a repository has been indexed for the first time, updates should be indexed much more quickly (typically within 5 minutes).

12
data/reusables/copilot/install-copilot-and-chat-combo-vs-procedure.md
View File

@@ -1,12 +0,0 @@
### Installing the combined {% data variables.product.prodname_copilot_short %} and {% data variables.product.prodname_copilot_chat_short %} extension in {% data variables.product.prodname_vs %} for versions 17.10 Preview 3 and later
1. Download the latest preview version of {% data variables.product.prodname_vs %} 2022 17.10 from [Visual Studio Release Notes](https://learn.microsoft.com/en-us/visualstudio/releases/2022/release-notes-preview) in the Microsoft documentation.
1. Follow the on-screen instructions to install {% data variables.product.prodname_vs %}.
1. When {% data variables.product.prodname_vs %} Installer launches, select the workloads you require, and then under "Installation details", expand the **Individual components** details and select **GitHub Copilot**.
![Screenshot of the {% data variables.product.prodname_vs %} Installer. The {% data variables.product.prodname_copilot %} component is highlighted with an orange outline.](/assets/images/help/copilot/install-copilot-extension-visual-studio-17-10.png)
1. In the bottom-right corner of {% data variables.product.prodname_vs %} Installer, click **Modify**.
1. When the modification is complete, close the {% data variables.product.prodname_vs %} Installer and launch {% data variables.product.prodname_vs %}.
1. Optionally, to modify the installation or add more components, launch {% data variables.product.prodname_vs %} Installer from the Windows Start menu.
* To the right of your installed version of {% data variables.product.prodname_vs %}, click **Modify**.
* Make your desired changes, and in the bottom right corner click **Modify** again to apply them.

1
data/reusables/copilot/install-copilot-vs-intro.md
View File

@@ -1 +0,0 @@
With {% data variables.product.prodname_vs %} version 17.10 Preview 3 or later, you can install a single extension that combines {% data variables.product.prodname_copilot %} and {% data variables.product.prodname_copilot_chat %}. If you use {% data variables.product.prodname_vs %} 17.8 or 17.9, you must install the {% data variables.product.prodname_copilot %} and {% data variables.product.prodname_copilot_chat %} extensions separately. The {% data variables.product.prodname_copilot %} extension is a prerequisite for using {% data variables.product.prodname_copilot_chat %}. For more information about the {% data variables.product.prodname_vs %} 17.10 Preview 3 release, see the [Visual Studio Release Notes](https://learn.microsoft.com/en-us/visualstudio/releases/2022/release-notes-preview#17100-pre30--visual-studio-2022-version-1710-preview-3) in the Microsoft documentation.

18
data/reusables/copilot/installing-copilot-in-jetbrains-ide.md
View File

@@ -1,18 +0,0 @@
To use {% data variables.product.prodname_copilot %} in a JetBrains IDE, you must install the {% data variables.product.prodname_copilot %} plugin.
{% data reusables.copilot.jetbrains-settings-preferences %}
1. In the left-side menu of the **Settings/Preferences** dialog box, click **Plugins**.
1. At the top of the **Settings/Preferences** dialog box, click **Marketplace**. In the search bar, search for **{% data variables.product.prodname_copilot %}**, then click **Install**.
![Screenshot of the "Preferences" window. A tab labeled "Marketplace" is highlighted with an orange outline. In a list of search results, the installed "GitHub Copilot" plugin is marked by a selected checkbox.](/assets/images/help/copilot/jetbrains-marketplace.png)
1. After {% data variables.product.prodname_copilot %} is installed, click **Restart IDE**.
1. After your JetBrains IDE has restarted, click the **Tools** menu. Click **{% data variables.product.prodname_copilot %}**, then click **Login to {% data variables.product.prodname_dotcom %}**.
![Screenshot of the expanded "Tools" menu and "{% data variables.product.prodname_copilot %}" sub-menu. The "Login to {% data variables.product.prodname_dotcom %}" option is highlighted in blue.](/assets/images/help/copilot/jetbrains-tools-menu.png)
1. In the "Sign in to {% data variables.product.prodname_dotcom %}" dialog box, to copy the device code and open the device activation window, click **Copy and Open**.
![Screenshot of the "Sign in to {% data variables.product.prodname_dotcom %}" dialog. A device code is displayed above a button labeled "Copy and Open".](/assets/images/help/copilot/device-code-copy-and-open.png)
1. A device activation window will open in your browser. Paste the device code, then click **Continue**.
1. {% data variables.product.prodname_dotcom %} will request the necessary permissions for {% data variables.product.prodname_copilot %}. To approve these permissions, click **Authorize {% data variables.product.prodname_copilot %} Plugin**.
1. After the permissions have been approved, your JetBrains IDE will show a confirmation. To begin using {% data variables.product.prodname_copilot %}, click **OK**.

1
data/reusables/copilot/link-to-vs-docs.md
View File

@@ -1 +0,0 @@
For an alternative installation method, you can also use the Microsoft instructions to install the {% data variables.product.prodname_copilot %} extension. For more information, see [Installation instructions](https://learn.microsoft.com/en-gb/visualstudio/ide/visual-studio-github-copilot-install-and-states?view=vs-2022) in the Microsoft documentation.

1
data/reusables/copilot/model-picker-enable-preview-features.md
View File

@@ -1 +0,0 @@
1. If you access {% data variables.product.prodname_copilot_chat_short %} through a {% data variables.product.prodname_copilot_for_business %}{% ifversion ghec %} or {% data variables.product.prodname_copilot_enterprise %}{% endif %} subscription, your organization{% ifversion ghec %} or enterprise{% endif %} must enable preview features for {% data variables.product.prodname_copilot_short %}. See "[AUTOTITLE](/copilot/managing-copilot/managing-github-copilot-in-your-organization/setting-policies-for-copilot-in-your-organization/managing-policies-for-copilot-in-your-organization){% ifversion ghec %}" or "[AUTOTITLE](/copilot/managing-copilot/managing-copilot-for-your-enterprise/managing-policies-and-features-for-copilot-in-your-enterprise){% endif %}."

1
data/reusables/copilot/procedural-intro.md
View File

@@ -1 +0,0 @@
{% data variables.product.prodname_copilot %} offers coding suggestions as you type in your coding environment. For more information about other things that {% data variables.product.prodname_copilot_short %} can do, see "[AUTOTITLE](/copilot/about-github-copilot/what-is-github-copilot)."

1
data/reusables/copilot/save-settings.md
View File

@@ -1 +0,0 @@
1. To confirm your new settings, click **Save**.

1
data/reusables/copilot/see-alternative-suggestions.md
View File

@@ -1 +0,0 @@
1. Optionally, you can see alternative suggestions, if any are available.

6
data/reusables/copilot/signup-procedure-enterprise.md
View File

@@ -1,6 +0,0 @@
1. Go to the [{% data variables.product.prodname_copilot_for_business %} sign up page](https://github.com/github-copilot/business_signup/choose_business_type).
1. To purchase {% data variables.product.prodname_copilot %} for your enterprise, select **Enable {% data variables.product.prodname_copilot %} at an enterprise level** and click **Continue**.
1. Select the enterprise for which you want to purchase {% data variables.product.prodname_copilot %} and click **Continue**.
1. Follow the steps to confirm your payment details, then click **Save**.
If you don't have a payment method on file, you'll be prompted to add one.

1
data/reusables/copilot/supported-tools.md
View File

@@ -1 +0,0 @@
{% data variables.product.prodname_copilot %} is available as an extension in {% data variables.product.prodname_vscode %}, Visual Studio, Vim, Neovim, the JetBrains suite of IDEs, and Azure Data Studio. For more information on using {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vscode %}, Visual Studio, Vim, Neovim, and JetBrains, see "[AUTOTITLE](/copilot/using-github-copilot/getting-started-with-github-copilot)." For more information on using {% data variables.product.prodname_copilot %} in Azure Data Studio, see [GitHub Copilot extension](https://learn.microsoft.com/en-us/sql/azure-data-studio/extensions/github-copilot-extension?view=sql-server-ver16) in Microsoft Learn.

1
data/reusables/copilot/test-content-exclusions-chat.md
View File

@@ -1 +0,0 @@
1. Ask {% data variables.product.prodname_copilot_chat_short %} a question about the excluded file. If your content is excluded successfully, {% data variables.product.prodname_copilot_short %} will be unable to answer your question, and will explain that some files were excluded from the conversation due to content exclusion rules.

1
data/reusables/copilot/vs-exit-and-relaunch.md
View File

@@ -1 +0,0 @@
1. Close the "Manage Extensions" window, then exit and relaunch {% data variables.product.prodname_vs %}.

3
data/reusables/copilot/vs-extensions.md
View File

@@ -1,3 +0,0 @@
1. In the {% data variables.product.prodname_vs %} menu bar, click **Extensions**, then click **Manage Extensions**.
![Screenshot of the menu bar in {% data variables.product.prodname_vs %}. The "Extensions" menu is open, and the "Manage Extensions" option is highlighted with an orange outline.](/assets/images/help/copilot/visual-studio-toolbar.png)

1
data/reusables/data-residency/about-enterprise-owners.md
View File

@@ -1 +0,0 @@
Enterprise owners are administrators who have complete control over your enterprise on {% data variables.enterprise.data_residency_site %}.

0
data/reusables/data-residency/data-resident-enterprise-prerequisite-access.md
View File

1
data/reusables/data-residency/data-resident-enterprise-prerequisite-setup-user.md
View File

@@ -1 +0,0 @@
You must have the credentials for your enterprise's setup user.

1
data/reusables/data-residency/data-resident-enterprise-sign-in-as-setup-user.md
View File

@@ -1 +0,0 @@
1. Sign in to your enterprise on {% data variables.enterprise.data_residency_site %} as the setup user.

1
data/reusables/data-residency/sign-in-to-okta.md
View File

@@ -1 +0,0 @@
1. Sign in to the Okta Admin Console.

5
data/reusables/data-residency/sso-recovery-codes-warning.md
View File

@@ -1,5 +0,0 @@
{% warning %}
**Warning**: Ensure you have downloaded and stored the SSO recovery codes for your enterprise's setup user. See "[Prerequisites](#prerequisites)."
{% endwarning %}

2
data/reusables/data-residency/test-sign-in.md
View File

@@ -1,2 +0,0 @@
1. If you are already signed in to {% data variables.enterprise.data_residency_site %} as the setup user, sign out.
1. Sign in using the account you assigned as the first enterprise owner.

5
data/reusables/dependabot/dependabot-grouped-security-updates-beta-note.md
View File

@@ -1,5 +0,0 @@
{% note %}
**Note:** Grouped pull requests for {% data variables.product.prodname_dependabot_security_updates %} are in {% data variables.release-phases.public_preview %} and subject to change.
{% endnote %}

9
data/reusables/dependabot/dependabot-version-updates-groups-beta.md
View File

@@ -1,9 +0,0 @@
{% ifversion dependabot-version-updates-groups %}
{% note %}
**Note:** {% data variables.product.prodname_dependabot %} grouped updates are currently in {% data variables.release-phases.public_preview %} and is subject to change.
{% endnote %}
{% endif %}

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