[aw] Goal failed
- Langage dominant
- Python
- Étoiles
- 10
- Forks
- 2
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
### Workflow Failure
**Workflow:** [Goal](#)
**Branch:** main
**Run:** https://github.com/githubnext/goal/actions/runs/29960307376
> [!WARNING]
> **Engine Failure**: The `copilot` engine terminated unexpectedly.
**Last agent output:**
```
Authentication failed with provider at http://172.30.0.30:10002 (HTTP 401).
Check your COPILOT_PROVIDER_API_KEY or COPILOT_PROVIDER_BEARER_TOKEN.
Changes +0 -0
Duration 1s
```
### Action Required
**Assign this issue to an agent** to debug and fix the issue.
Debug with any coding agent
Use this prompt with any coding agent (GitHub Copilot, Claude, Gemini, etc.):
````
Debug the agentic workflow failure using https://raw.githubusercontent.com/github/gh-aw/main/debug.md
The failed workflow run is at https://github.com/githubnext/goal/actions/runs/29960307376
````
Manually invoke the agent
Debug this workflow failure using your favorite Agent CLI and the `agentic-workflows` prompt.
- Start your agent
- Load the `agentic-workflows` skill from `.github/skills/agentic-workflows/SKILL.md` or
- Type `debug the agentic workflow goal failure in https://github.com/githubnext/goal/actions/runs/29960307376`
> [!TIP]
>
> Stop reporting this workflow as a failure
>
> To stop a workflow from creating failure issues, set `report-failure-as-issue: false` in its frontmatter:
> ```yaml
> safe-outputs:
> report-failure-as-issue: false
> ```
>
>
> Generated from [Goal](https://github.com/githubnext/goal/actions/runs/29960307376) · [◷](https://github.com/search?q=repo%3Agithubnext%2Fgoal+is%3Aissue+%22gh-aw-workflow-id%3A+goal%22&type=issues)
> - [x] expires on Jul 29, 2026, 9:47 PM UTC
Guide de contribution
Aucun guide de contribution indexé pour ce dépôt
Piste de recherche
Commencez par l’exécution échouée du workflow Goal et l’erreur d’authentification affichée dans cette issue, puis consultez debug.md et .github/skills/agentic-workflows/SKILL.md. Suivez la configuration de COPILOT_PROVIDER_API_KEY ou de COPILOT_PROVIDER_BEARER_TOKEN et vérifiez qu’une nouvelle exécution se termine sans l’échec HTTP 401.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- github-actions
- Domaine
- ci-cd
- Type d'issue
- Bug
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- Calme
- Clarté
- À clarifier
- Accessibilité débutants
- 35/100