githubnext / githubnext/gh-aw-cao
[aw] PR Sous Chef hit Copilot organization billing error
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 1
- Avg merge
- 49m
- Merged PRs (30d)
- 837
Description
### Workflow Failure
**Workflow:** [PR Sous Chef](https://github.com/githubnext/gh-aw-cao/blob/main/.github/workflows/pr-sous-chef.md)
**Branch:** main
**Run:** https://github.com/githubnext/gh-aw-cao/actions/runs/35117212430
> [!WARNING]
> **Copilot organization billing is unavailable**: The workflow uses `permissions.copilot-requests: write`, but GitHub Copilot rejected the built-in `GITHUB_TOKEN`.
To resolve this:
1. Ask an organization owner to check **Organization settings → Copilot → Policies → Copilot CLI** and enable **Allow use of Copilot CLI billed to the organization**.
2. If organization billing is unavailable, use individual billing instead: set `permissions.copilot-requests: none`, configure a `COPILOT_GITHUB_TOKEN` repository secret with a fine-grained personal access token from a user with an active Copilot subscription, and recompile the workflow.
See [Copilot billing](https://github.github.com/gh-aw/reference/billing/) for complete setup instructions.
> [!WARNING]
> **Code Push Failed**: A code push safe output failed, and subsequent safe outputs were cancelled.
**Code Push Errors:**
- `push_to_pull_request_branch`: Failed to push changes: ERR_SYSTEM: pushSignedCommits: failed to rebase commit range onto current GraphQL parent (2021780d4ab68570a4bf6b89189e11fc4d52f795). Resolve conflicts by rebasing/cherry-picking locally and retry. Root cause: Auto-merging dashboard/site/src/data/queries/declarative.js
- `CONFLICT (content)`: Merge conflict in dashboard/site/src/data/queries/declarative.js
- `CONFLICT (content)`: Merge conflict in dashboard/site/test/unit/data-queries.test.js
- `CONFLICT (content)`: Merge conflict in dashboard/site/test/unit/validator.test.js
- `Rebasing (1/3)
error`: could not apply 9497de1b... Add filtered dashboard query aggregations
- `hint`: Resolve all conflicts manually, mark them as resolved with
- `hint`: "git add/rm ", then run "git rebase --continue".
- `hint`: You can instead skip this commit: run "git rebase --skip".
- `hint`: To abort and get back to the state before "git rebase", run "git rebase --abort".
- `hint`: Disable this message with "git config set advice.mergeConflict false"
- `push_to_pull_request_branch`: Failed to push changes: ERR_SYSTEM: pushSignedCommits: failed to rebase commit range onto current GraphQL parent (2307085897c551f810069fc3e5599d1fa31312ee). Resolve conflicts by rebasing/cherry-picking locally and retry. Root cause: Auto-merging dashboard/site/src/components/data-view.js
- `CONFLICT (content)`: Merge conflict in dashboard/site/src/components/data-view.js
- `CONFLICT (content)`: Merge conflict in dashboard/site/src/presenter.js
- `Rebasing (1/3)
error`: could not apply 637907ad... Add mobile card-list rendering
- `hint`: Resolve all conflicts manually, mark them as resolved with
- `hint`: "git add/rm ", then run "git rebase --continue".
- `hint`: You can instead skip this commit: run "git rebase --skip".
- `hint`: To abort and get back to the state before "git rebase", run "git rebase --abort".
- `hint`: Disable this message with "git config set advice.mergeConflict false"
**Agent Timed Out**: The agent job exceeded the maximum allowed execution time (15 minutes).
To increase the timeout, add or update the `timeout-minutes` setting in your workflow's frontmatter:
```yaml
---
timeout-minutes: 25
---
```
### Action Required
**Assign this issue to an agent** to debug and fix the issue.
Optimize token consumption
This failure was triggered by a guardrail limit (max-turns / timeout). Use this prompt with any coding agent (GitHub Copilot, Claude, Gemini, etc.) to analyze token usage and reduce costs:
````
Optimize the agentic workflow token consumption using https://raw.githubusercontent.com/github/gh-aw/main/optimize.md
The workflow run is at https://github.com/githubnext/gh-aw-cao/actions/runs/35117212430
````
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/gh-aw-cao/actions/runs/35117212430
````
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 pr-sous-chef failure in https://github.com/githubnext/gh-aw-cao/actions/runs/35117212430`
> [!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 [PR Sous Chef](https://github.com/githubnext/gh-aw-cao/actions/runs/35117212430) · copilot · 302.2 AIC · [◷](https://github.com/search?q=repo%3Agithubnext%2Fgh-aw-cao+is%3Aissue+%22gh-aw-workflow-id%3A+pr-sous-chef%22&type=issues)
> - [x] expires on Sep 17, 2026, 4:05 PM UTC
Contributor guide
Research direction
Start by inspecting .github/workflows/pr-sous-chef.md and the referenced failed run to determine which failure is in scope: Copilot billing, timeout, or push conflicts. Review the listed conflicted JavaScript files and workflow frontmatter, then rerun PR Sous Chef; done means the selected failure no longer occurs and the workflow reports success.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, javascript
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100