Skip to content

Commit fd08646

Browse files
docs-botdocs-bot
authored
Merge pull request #40047 from github/repo-sync
Repo sync
2 parents 7f9ac8b + ebfc43b commit fd08646

File tree

5 files changed

+39
-2
lines changed

5 files changed

+39
-2
lines changed

‎content/admin/data-residency/feature-overview-for-github-enterprise-cloud-with-data-residency.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,6 @@ The following features are currently unavailable on {% data variables.enterprise
2626
| Maven and Gradle support for {% data variables.product.prodname_registry %} | Currently unavailable. | [AUTOTITLE](/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry) |
2727
| {% data variables.product.prodname_importer %} (the "Import repository" button on {% data variables.product.prodname_dotcom_the_website %}) | Instead, the **{% data variables.product.prodname_importer_proper_name %}** is available to migrate data. See [AUTOTITLE](/migrations/using-github-enterprise-importer/understanding-github-enterprise-importer/about-github-enterprise-importer). | [AUTOTITLE](/migrations/importing-source-code/using-github-importer/about-github-importer) |
2828
| {% data variables.product.prodname_copilot_short %} Metrics API | Currently unavailable | [AUTOTITLE](/rest/copilot/copilot-metrics) |
29-
| {% data variables.copilot.copilot_coding_agent %} | Currently unavailable | [AUTOTITLE](/copilot/concepts/about-copilot-coding-agent) |
3029
| Restricting {% data variables.product.prodname_actions %} policies to verified creators | Currently unavailable | [AUTOTITLE](/admin/enforcing-policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#allow-enterprise-and-select-non-enterprise-actions-and-reusable-workflows) |
3130
| {% data variables.product.prodname_github_models %} | Currently unavailable | [AUTOTITLE](/github-models/about-github-models) |
3231
| Some features currently in {% data variables.release-phases.public_preview %} or {% data variables.release-phases.private_preview %} | Certain features that are in a preview phase on {% data variables.product.prodname_dotcom_the_website %} may not be available on {% data variables.enterprise.data_residency_site %} | |

‎content/copilot/concepts/coding-agent/coding-agent.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -136,7 +136,6 @@ Users can include hidden messages in issues assigned to {% data variables.produc
136136
* **{% data variables.copilot.copilot_coding_agent %} does not work in personal repositories owned by {% data variables.enterprise.prodname_managed_users %}**. This is because {% data variables.copilot.copilot_coding_agent %} requires {% data variables.product.company_short %}-hosted runners, which are not available to repositories owned by {% data variables.enterprise.prodname_managed_users %}. See [AUTOTITLE](/actions/using-github-hosted-runners/using-github-hosted-runners/about-github-hosted-runners).
137137
* **{% data variables.product.prodname_copilot_short %} doesn't account for content exclusions**. Content exclusions allow administrators to configure {% data variables.product.prodname_copilot_short %} to ignore certain files. When using {% data variables.copilot.copilot_coding_agent %}, {% data variables.product.prodname_copilot_short %} will not ignore these files, and will be able to see and update them. See [AUTOTITLE](/copilot/managing-copilot/configuring-and-auditing-content-exclusion/excluding-content-from-github-copilot).
138138
* **{% data variables.copilot.copilot_coding_agent %} does not apply the "Suggestions matching public code" policy**. {% data variables.product.prodname_copilot_short %} may still produce suggestions matching public code, even if the "Suggestions matching public code" policy is set to "Block." If this happens, {% data variables.product.prodname_copilot_short %} will not provide code references pointing to the original source of the code. See [AUTOTITLE](/copilot/managing-copilot/managing-copilot-as-an-individual-subscriber/managing-your-copilot-plan/managing-copilot-policies-as-an-individual-subscriber#enabling-or-disabling-suggestions-matching-public-code).
139-
* **{% data variables.copilot.copilot_coding_agent %} is not available in {% data variables.enterprise.data_residency %}**. The agent is only available in {% data variables.product.prodname_dotcom_the_website %}.
140139
* **{% data variables.copilot.copilot_coding_agent %} only works with repositories hosted on {% data variables.product.github %}**. If your repository is stored using a different code hosting platform, {% data variables.product.prodname_copilot_short %} won't be able to work on it.
141140

142141
## Hands-on practice

‎content/copilot/tutorials/enhance-agent-mode-with-mcp.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -196,3 +196,4 @@ Try the [Integrate MCP with {% data variables.product.prodname_copilot %}](https
196196
## Further reading
197197

198198
* **MCP fundamentals**: For more information about setting up and configuring MCP servers, see [AUTOTITLE](/copilot/customizing-copilot/using-model-context-protocol/extending-copilot-chat-with-mcp).
199+
* **Using MCP servers**: For additional ideas on integrating MCP with {% data variables.product.prodname_copilot %}, see [5 ways to transform your workflow using GitHub Copilot and MCP](https://github.blog/ai-and-ml/github-copilot/5-ways-to-transform-your-workflow-using-github-copilot-and-mcp/) on the {% data variables.product.prodname_blog %}.

‎content/issues/tracking-your-work-with-issues/administering-issues/index.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,7 @@ versions:
88
topics:
99
- Issues
1010
children:
11+
- /triaging-an-issue-with-ai
1112
- /pinning-an-issue-to-your-repository
1213
- /marking-issues-or-pull-requests-as-a-duplicate
1314
- /transferring-an-issue-to-another-repository

‎content/issues/tracking-your-work-with-issues/administering-issues/triaging-an-issue-with-ai.md

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
---
2+
title: Triaging an issue with AI
3+
intro: 'Use AI to triage new issues and determine whether the issue is actionable or needs more information.'
4+
permissions: 'Anyone on {% data variables.product.prodname_dotcom_the_website %} can configure AI triaging in any repository they have admin access to.'
5+
versions:
6+
fpt: '*'
7+
ghec: '*'
8+
topics:
9+
- Issues
10+
- Project management
11+
shortTitle: Triage an issue
12+
---
13+
14+
## About the AI-powered issue intake tool
15+
16+
The AI-powered issue intake tool helps you automate the triage process for new issues in your repository. Open source maintainers and project managers are often inundated with new issues, many of which may lack necessary information, or are not actionable. This tool leverages AI to analyze incoming issues and provide suggestions for triaging them, helping you manage your issue backlog more effectively.
17+
18+
## Enabling the AI-powered issue intake tool
19+
20+
The AI-powered issue intake tool is a {% data variables.product.github %} action that you can enable in your repository. For more information about {% data variables.product.github %} actions, see [AUTOTITLE](/actions/get-started/understand-github-actions).
21+
22+
1. Visit the [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace).
23+
1. Search for and select "AI-powered issue intake tool."
24+
1. On the action's {% data variables.product.prodname_marketplace %} page, follow the setup instructions to install the action in your repository.
25+
1. Optionally, customize the action's configuration file based on the guidance provided on the action's {% data variables.product.prodname_marketplace %} page.
26+
27+
## Using the AI-powered issue intake tool
28+
29+
If you are using the default configuration of the AI-powered issue intake tool, the action will be triggered when the `request ai review` label is applied to an issue. For information on creating a label, see [AUTOTITLE](/issues/using-labels-and-milestones-to-track-work/managing-labels#creating-a-label). Once triggered, the tool will analyze the issue and provide suggestions for triaging it.
30+
31+
1. Navigate to the "Issues" tab in your repository.
32+
1. Open a new or existing issue that you want to triage.
33+
1. Add the AI labels that map to the analyses you want the tool to perform.
34+
1. Apply the `request ai review` label to the issue.
35+
1. Wait for the action to complete. You can monitor the progress in the "Actions" tab of your repository.
36+
1. Once the action is complete, check the issue for comments or labels added by the AI-powered issue intake tool. The tool may suggest actions such as requesting more information, or marking it as actionable.
37+
1. Review the suggestions provided by the tool and take appropriate action on the issue.

0 commit comments

Comments
 (0)