Skip to content

Commit d88f871

Browse files
committed
Remove copilot workspace references
1 parent db74c34 commit d88f871

File tree

11 files changed

+15
-69
lines changed

11 files changed

+15
-69
lines changed

content/code-security/code-scanning/managing-code-scanning-alerts/resolving-code-scanning-alerts.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -43,6 +43,7 @@ With a {% data variables.copilot.copilot_enterprise %} license, you can ask {% d
4343
{% data reusables.repositories.navigate-to-repo %}
4444
{% data reusables.repositories.sidebar-security %}
4545
{% data reusables.repositories.sidebar-code-scanning-alerts %}
46+
4647
1. Click the name of an alert.
4748
1. If {% data variables.copilot.copilot_autofix_short %} can suggest a fix, at the top of the page, click **{% octicon "shield-check" aria-hidden="true" aria-label="shield-check" %} Generate fix**.
4849
1. Once the suggested fix has been generated, at the bottom of the page, you can click **Create PR with fix** to automatically generate a pull request with the suggested fix.
@@ -93,6 +94,7 @@ To dismiss alerts:
9394
{% data reusables.repositories.navigate-to-repo %}
9495
{% data reusables.repositories.sidebar-security %}
9596
{% data reusables.repositories.sidebar-code-scanning-alerts %}
97+
9698
1. If you want to dismiss an alert, it's important to explore the alert first, so that you can choose the correct dismissal reason. Click the alert you'd like to explore.
9799
1. Review the alert, then click **Dismiss alert** and choose, or type, a reason for closing the alert.
98100
![Screenshot of an alert check failure. The "Dismiss alert" button is highlighted in dark orange and the dismiss drop-down displayed. ](/assets/images/help/repository/code-scanning-alert-dropdown-reason.png)
@@ -115,6 +117,7 @@ You may have multiple code scanning configurations on a single repository. When
115117
{% data reusables.repositories.navigate-to-repo %}
116118
{% data reusables.repositories.sidebar-security %}
117119
{% data reusables.repositories.sidebar-code-scanning-alerts %}
120+
118121
1. Under "{% data variables.product.prodname_code_scanning_caps %}", click a {% data variables.product.prodname_code_scanning %} alert.
119122
1. In the "Affected branches" section of the sidebar, click the desired branch.
120123
1. In the "Configurations analyzing" dialog, review details of the configurations that reported this alert on the selected branch. To delete an unwanted configuration for the desired branch, click {% octicon "trash" aria-label="Delete configuration" %}.
@@ -128,6 +131,7 @@ You may have multiple code scanning configurations on a single repository. When
128131
If you save your changes after accidentally deleting a configuration, re-run the configuration to update the alert. For more information on re-running configurations that use {% data variables.product.prodname_actions %}, see [AUTOTITLE](/actions/managing-workflow-runs/re-running-workflows-and-jobs#re-running-all-the-jobs-in-a-workflow).
129132

130133
> [!NOTE]
134+
>
131135
> * If you remove all {% data variables.product.prodname_code_scanning %} configurations for the default branch of your repository, the default branch will remain in the "Affected branches" sidebar, but it will not be analyzed by any configurations.
132136
> * If you remove all {% data variables.product.prodname_code_scanning %} configurations for any branch other than the default branch of your repository, that branch will be removed from the "Affected branches" sidebar.
133137
@@ -136,6 +140,3 @@ You may have multiple code scanning configurations on a single repository. When
136140
* [AUTOTITLE](/code-security/code-scanning/managing-code-scanning-alerts/triaging-code-scanning-alerts-in-pull-requests)
137141
* [AUTOTITLE](/code-security/code-scanning/enabling-code-scanning/configuring-default-setup-for-code-scanning)
138142
* [AUTOTITLE](/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning)
139-
{%- ifversion copilot-hadron %}
140-
* [AUTOTITLE](/copilot/using-github-copilot/using-github-copilot-for-pull-requests/using-copilot-to-help-you-work-on-a-pull-request)
141-
{%- endif %}

content/code-security/code-scanning/managing-code-scanning-alerts/responsible-use-autofix-code-scanning.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -115,8 +115,6 @@ The best way to mitigate the limitations of suggestions from {% data variables.c
115115

116116
It is important to remember that the author of a pull request retains responsibility for how they respond to review comments and suggested code changes, whether proposed by colleagues or automated tools. Developers should always look at suggestions for code changes critically. If needed, they should edit the suggested changes to ensure that the resulting code and application are correct, secure, meet performance criteria, and satisfy all other functional and non-functional requirements for the application.
117117

118-
{% data reusables.rai.code-scanning.copilot-workspaces-prs-autofix-note %}
119-
120118
## Next steps
121119

122120
* [AUTOTITLE](/code-security/code-scanning/managing-code-scanning-alerts/about-code-scanning-alerts)

content/code-security/code-scanning/managing-code-scanning-alerts/triaging-code-scanning-alerts-in-pull-requests.md

Lines changed: 1 addition & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -127,6 +127,7 @@ Anyone with push access to a pull request can fix a {% data variables.product.pr
127127
When {% data variables.copilot.copilot_autofix_short %} is enabled for a repository, alerts are displayed in pull requests as normal and information from any alerts found by {% data variables.product.prodname_code_scanning %} is automatically sent to the LLM for processing. When LLM analysis is complete, any results are published as comments on relevant alerts. For more information, see [AUTOTITLE](/code-security/code-scanning/managing-code-scanning-alerts/responsible-use-autofix-code-scanning).
128128

129129
> [!NOTE]
130+
>
130131
> * {% data variables.copilot.copilot_autofix_short %} supports a subset of {% data variables.product.prodname_codeql %} queries. For information about the availability of {% data variables.copilot.copilot_autofix_short %}, see the query tables linked from [AUTOTITLE](/code-security/code-scanning/managing-your-code-scanning-configuration/codeql-query-suites#query-lists-for-the-default-query-suites).
131132
> * When analysis is complete, all relevant results are published to the pull request at once. If at least one alert in your pull request has an {% data variables.copilot.copilot_autofix_short %} suggestion, you should assume that the LLM has finished identifying potential fixes for your code.
132133
> * On alerts generated from queries that are not supported by {% data variables.copilot.copilot_autofix_short %}, you will see a note telling you that the query is not supported. If a suggestion for a supported query fails to generate, you will see a note on the alert prompting you to try pushing another commit or to contact support.
@@ -143,8 +144,6 @@ Each {% data variables.copilot.copilot_autofix_short %} suggestion demonstrates
143144
* Under **Edit with {% data variables.product.prodname_cli %}**, follow the instructions for checking out the pull request locally and applying the suggested fix.
144145
* Select **Edit FILENAME** to edit the file directly on {% data variables.product.prodname_dotcom %} with the suggested fix applied.
145146

146-
{% data reusables.rai.code-scanning.copilot-workspaces-prs-autofix-note %}
147-
148147
1. Optionally, if you prefer to apply the fix on a local repository or branch, select the {% octicon "copy" aria-hidden="true" aria-label="copy" %} dropdown menu on the suggestion.
149148
* Select **View autofix patch** to display instructions for applying the suggested fix to any local repository or branch.
150149
* Select **Copy modified line LINE_NUMBER** to copy a specific line of the suggestion.
@@ -171,7 +170,3 @@ An alternative way of closing an alert is to dismiss it. You can dismiss an aler
171170
For more information about dismissing alerts, see [AUTOTITLE](/code-security/code-scanning/managing-code-scanning-alerts/resolving-code-scanning-alerts#dismissing--alerts).
172171

173172
## Further reading
174-
175-
{%- ifversion copilot-hadron %}
176-
* [AUTOTITLE](/copilot/using-github-copilot/using-github-copilot-for-pull-requests/using-copilot-to-help-you-work-on-a-pull-request)
177-
{%- endif %}

content/copilot/about-github-copilot/github-copilot-features.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -40,10 +40,6 @@ AI-generated code review suggestions to help you write better code. See [AUTOTIT
4040

4141
AI-generated summaries 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. See [AUTOTITLE](/copilot/using-github-copilot/using-github-copilot-for-pull-requests/creating-a-pull-request-summary-with-github-copilot).
4242

43-
### {% data variables.copilot.copilot_workspace %} ({% data variables.release-phases.public_preview %})
44-
45-
A {% data variables.product.prodname_copilot_short %}-enabled environment for refining your pull requests, validating changes, and integrating suggestions from reviewers. See [AUTOTITLE](/copilot/using-github-copilot/using-github-copilot-for-pull-requests/using-copilot-to-help-you-work-on-a-pull-request).
46-
4743
### {% data variables.copilot.copilot_autocomplete_pr %} ({% data variables.release-phases.public_preview %})
4844

4945
AI-generated text completion to help you write pull request descriptions quickly and accurately. See [AUTOTITLE](/copilot/using-github-copilot/using-copilot-text-completion).

content/copilot/quickstart.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,8 +26,6 @@ topics:
2626

2727
You can use {% data variables.product.prodname_copilot_short %} to get answers to coding-related questions, such as how best to code something, how to fix a bug, or how someone else's code works. For full details of what {% data variables.product.prodname_copilot_short %} can do, see [AUTOTITLE](/copilot/about-github-copilot/what-is-github-copilot).
2828

29-
If you have access to {% data variables.copilot.copilot_workspace %}, {% data variables.product.prodname_copilot_short %} can also help you when you are editing files in a pull request on the {% data variables.product.github %} website by offering you code completion suggestions. For more information about {% data variables.copilot.copilot_workspace %}, see [AUTOTITLE](/copilot/using-github-copilot/using-github-copilot-for-pull-requests/using-copilot-to-help-you-work-on-a-pull-request).
30-
3129
Instructions for using {% data variables.product.prodname_copilot_short %} differ depending on where you are using it. This version of the quickstart is for {% data variables.product.github %}. Click the tabs above for instructions on using {% data variables.product.prodname_copilot_short %} in other environments.
3230

3331
{% ifversion fpt %}
@@ -95,6 +93,7 @@ Instructions for using {% data variables.product.prodname_copilot_short %} diffe
9593
## Prerequisites
9694

9795
{% ifversion ghec %}
96+
9897
* **Subscription to {% data variables.product.prodname_copilot_short %}**. To use {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_windows_terminal %}, you must have an active {% data variables.product.prodname_copilot %} subscription. {% data reusables.copilot.subscription-prerequisite %}
9998
{% endif %}
10099
* **{% data variables.product.prodname_windows_terminal %} Canary**. Terminal Chat is only available in [{% data variables.product.prodname_windows_terminal %} Canary](https://github.com/microsoft/terminal?tab=readme-ov-file#installing-windows-terminal-canary).
@@ -145,6 +144,7 @@ Instructions for using {% data variables.product.prodname_copilot_short %} diffe
145144
## Prerequisites
146145

147146
{% ifversion ghec %}
147+
148148
* **{% data variables.product.prodname_copilot_short %} subscription** - To use {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vscode_shortname %}, you must have an active {% data variables.product.prodname_copilot %} subscription. {% data reusables.copilot.subscription-prerequisite %}
149149
{% endif %}
150150
{% data reusables.copilot.vscode-prerequisites %}
@@ -184,6 +184,7 @@ The following example uses JavaScript, however other languages will work similar
184184
## Next steps
185185

186186
{% data reusables.copilot.quickstart-nextsteps1 %}
187+
187188
* **Use {% data variables.product.prodname_copilot_short %} like a pro** - Learn how to write effective prompts for {% data variables.product.prodname_copilot %}. For more information, see [Best practices for using {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/copilot/prompt-crafting) in the {% data variables.product.prodname_vscode %} documentation.
188189
* **Get familiar with {% data variables.copilot.next_edit_suggestions %}** - See [About {% data variables.copilot.next_edit_suggestions %}](/copilot/using-github-copilot/getting-code-suggestions-in-your-ide-with-github-copilot#about-next-edit-suggestions).
189190
{% data reusables.copilot.quickstart-nextsteps2 %}
@@ -203,6 +204,7 @@ Instructions for using {% data variables.product.prodname_copilot_short %} diffe
203204
## Prerequisites
204205

205206
{% ifversion ghec %}
207+
206208
* **Subscription to {% data variables.product.prodname_copilot_short %}**. To use {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vs %}, you must have an active {% data variables.product.prodname_copilot %} subscription. {% data reusables.copilot.subscription-prerequisite %}
207209
{% endif %}
208210
{% data reusables.copilot.visual-studio-prerequisites %}
@@ -235,6 +237,7 @@ The following example uses JavaScript, however other languages will work similar
235237
## Next steps
236238

237239
{% data reusables.copilot.quickstart-nextsteps1 %}
240+
238241
* **Prompt like a pro** - Watch [{% data variables.product.prodname_vs %} Prompt Engineering with {% data variables.product.prodname_copilot %}](https://www.youtube.com/watch?v=9hZsOeIINg8&list=PLReL099Y5nRckZDdcQ21UigO9pKa14yxC) on YouTube.
239242
{% data reusables.copilot.quickstart-nextsteps2 %}
240243

@@ -253,6 +256,7 @@ Instructions for using {% data variables.product.prodname_copilot_short %} diffe
253256
## Prerequisites
254257

255258
{% ifversion ghec %}
259+
256260
* **Subscription to {% data variables.product.prodname_copilot_short %}**. To use {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vs %}, you must have an active {% data variables.product.prodname_copilot %} subscription. {% data reusables.copilot.subscription-prerequisite %}
257261
{% endif %}
258262
* **A compatible JetBrains IDE**. {% data variables.product.prodname_copilot_short %} is supported in a large number of JetBrains IDEs. For a full list, see [AUTOTITLE](/copilot/github-copilot-chat/copilot-chat-in-ides/using-github-copilot-chat-in-your-ide?tool=jetbrains).

content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md

Lines changed: 3 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -37,6 +37,7 @@ When you change the base repository, you also change notifications for the pull
3737
When you change any of the information in the branch range, the Commit and Files changed preview areas will update to show your new range.
3838

3939
> [!TIP]
40+
>
4041
> * Using the compare view, you can set up comparisons across any timeframe. For more information, see [AUTOTITLE](/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits).
4142
> * Project maintainers can add a pull request template for a repository. Templates include prompts for information in the body of a pull request. For more information, see [AUTOTITLE](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates).
4243
@@ -45,11 +46,13 @@ When you change any of the information in the branch range, the Commit and Files
4546
{% webui %}
4647

4748
{% data reusables.repositories.navigate-to-repo %}
49+
4850
1. In the "Branch" menu, choose the branch that contains your commits.
4951

5052
![Screenshot of the branch dropdown menu on the main page of a repository.](/assets/images/help/pull_requests/branch-dropdown.png)
5153

5254
{% data reusables.repositories.new-pull-request %}
55+
5356
1. Use the _base_ branch dropdown menu to select the branch you'd like to merge your changes into, then use the _compare_ branch drop-down menu to choose the topic branch you made your changes in.
5457
{% data reusables.repositories.pr-title-description %}
5558
{% data reusables.repositories.create-pull-request %}
@@ -185,14 +188,6 @@ You can also make changes to files on the {% data variables.product.github %} we
185188
1. In the menu, click **Edit file**.
186189
1. Make your changes in the editor and when committing your change, choose to commit directly back to your head branch.
187190

188-
{% ifversion copilot-hadron %}
189-
190-
If you are part of the {% data variables.release-phases.public_preview %} of {% data variables.copilot.copilot_workspace %}, clicking **Edit** on a file on the "Files changed" tab will open the file in a {% data variables.copilot.copilot_workspace %} on {% data variables.product.prodname_dotcom %}. In a {% data variables.copilot.copilot_workspace %}, you can still make changes to the file but also make changes to other files in the repository, group your changes into a single commit, and take advantage of {% data variables.product.prodname_copilot_short %} code completion.
191-
192-
You can access {% data variables.copilot.copilot_workspace %} by choosing to edit an individual file or by clicking **Open in {% data variables.copilot.copilot_workspace_short %}** in your pull request's right sidebar. For more information about {% data variables.copilot.copilot_workspace %} and joining the {% data variables.release-phases.public_preview %}, see [AUTOTITLE](/copilot/using-github-copilot/using-github-copilot-for-pull-requests/using-copilot-to-help-you-work-on-a-pull-request).
193-
194-
{% endif %}
195-
196191
{% endwebui %}
197192

198193
## Further reading

content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md

Lines changed: 1 addition & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -25,15 +25,10 @@ Organization members with write access can also assign a pull request review to
2525
> [!NOTE]
2626
> Pull request authors can't request reviews unless they are either a repository owner or collaborator with write access to the repository.
2727
28-
{% ifversion copilot-hadron %}
29-
30-
## Requesting reviews from collaborators and organization members
31-
32-
{% endif %}
33-
3428
You can request a review from either a suggested or specific person. Suggested reviewers are based on [git blame data](/repositories/working-with-files/using-files/viewing-a-file). If you request a review, other people with read access to the repository can still review your pull request. Once someone has reviewed your pull request and you've made the necessary changes, you can re-request review from the same reviewer. If the requested reviewer does not submit a review, and the pull request meets the repository's [mergeability requirements](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests), you can still merge the pull request.
3529

3630
{% data reusables.repositories.sidebar-pr %}
31+
3732
1. In the list of pull requests, click the pull request that you'd like to ask a specific person or a team to review.
3833
1. To request a review from a suggested person under **Reviewers**, next to their username, click **Request**.
3934

@@ -47,17 +42,6 @@ You can request a review from either a suggested or specific person. Suggested r
4742

4843
![Screenshot of the "Reviewers" section of a pull request's sidebar. To the right of @octocat, a sync icon is outlined in dark orange.](/assets/images/help/pull_requests/request-re-review.png)
4944

50-
{% ifversion copilot-hadron %}
51-
52-
## Requesting a review from {% data variables.product.prodname_copilot %}
53-
54-
>[!NOTE]
55-
>{% data variables.copilot.copilot_workspace %} is currently in {% data variables.release-phases.public_preview %}. For information about joining the {% data variables.release-phases.public_preview %}, see [AUTOTITLE](/copilot/using-github-copilot/using-github-copilot-for-pull-requests/using-copilot-to-help-you-work-on-a-pull-request).
56-
57-
You can also request that {% data variables.product.prodname_copilot_short %} reviews your code and provides feedback and suggested changes on your work. See [AUTOTITLE](/copilot/using-github-copilot/code-review/using-copilot-code-review).
58-
59-
{% endif %}
60-
6145
## Further reading
6246

6347
* [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)

0 commit comments

Comments
 (0)