Skip to content

Commit 5f5360c

Browse files
SiaraMistsunbrye
andauthored
Copilot Users Can Ask About a Failed Actions Job [GA] (#53914)
Co-authored-by: Sunbrye Ly <[email protected]>
1 parent a5ae7e2 commit 5f5360c

File tree

3 files changed

+30
-2
lines changed

3 files changed

+30
-2
lines changed

content/actions/monitoring-and-troubleshooting-workflows/troubleshooting-workflows/about-troubleshooting-workflows.md

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,16 @@ shortTitle: About troubleshooting
1212

1313
## Troubleshooting your workflows
1414

15+
There are several ways you can troubleshoot failed workflow runs.
16+
17+
{% ifversion copilot %}
18+
19+
### Using {% data variables.product.prodname_copilot %}
20+
21+
If a workflow run fails, you can open a chat with {% data variables.product.prodname_copilot %} for assistance resolving the error. See [AUTOTITLE](/actions/monitoring-and-troubleshooting-workflows/troubleshooting-workflows/using-copilot-to-troubleshoot-workflows).
22+
23+
{% endif %}
24+
1525
### Using workflow run logs
1626

1727
Each workflow run generates activity logs that you can view, search, and download. For more information, see [AUTOTITLE](/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs).
@@ -31,8 +41,6 @@ If you attempt to cancel a workflow and the cancellation doesn't succeed, make s
3141
To analyze the inefficiencies and reliability of your workflows using metrics, see [AUTOTITLE](/actions/administering-github-actions/viewing-github-actions-metrics).
3242
{% endif %}
3343

34-
## Monitoring self-hosted runners
35-
3644
## Troubleshooting self-hosted runners
3745

3846
If you use self-hosted runners, you can view their activity and diagnose common issues.

content/actions/monitoring-and-troubleshooting-workflows/troubleshooting-workflows/index.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,7 @@ versions:
88
ghec: '*'
99
children:
1010
- /about-troubleshooting-workflows
11+
- /using-copilot-to-troubleshoot-workflows
1112
- /enabling-debug-logging
1213
- /working-with-support-for-github-actions
1314
---
Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
---
2+
title: Using Copilot to troubleshoot workflows
3+
intro: 'You can use {% data variables.product.prodname_copilot %} to help resolve failed workflow runs.'
4+
versions:
5+
feature: copilot
6+
shortTitle: Use Copilot
7+
permissions: This feature is available for users on all {% data variables.product.prodname_copilot %} subscription tiers.
8+
---
9+
10+
If a workflow run fails, you can open a chat with {% data variables.product.prodname_copilot %} for assistance resolving the error.
11+
12+
To open a chat about a failed workflow run, you can either:
13+
14+
* Next to the failed check in the merge box, click **{% octicon "kebab-horizontal" aria-hidden="true" %}**, then click **{% octicon "copilot" aria-hidden="true" %} Explain error**.
15+
* In the merge box, click on the failed check. At the top of the workflow run summary page, click **{% octicon "copilot" aria-hidden="true" %} Explain error**.
16+
17+
This opens a chat window with {% data variables.product.prodname_copilot %}, where it will provide instructions to resolve the issue.
18+
19+
>[!NOTE] If you are on a {% data variables.product.prodname_copilot_free %} subscription, this will count towards your monthly chat message limit.

0 commit comments

Comments
 (0)