Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting
| - name: Close existing PRs | ||
| run: | | ||
| gh pr list --repo ${{ github.repository }} --state open --author "tscircuitbot" --json number,title --jq '.[] | select(.title | startswith("chore:")) | .number' | xargs -I{} gh pr close {} --comment "Closing in favor of a new update PR" |
There was a problem hiding this comment.
The new Close existing PRs step invokes gh pr close without exporting GH_TOKEN or GITHUB_TOKEN with write permissions. When a previous bot PR exists, this call will run with the default token (read‑only in most workflows) and gh fails with HTTP 403: Resource not accessible by integration, stopping the whole job before it can create the new update PR. The subsequent merge step already sets GH_TOKEN to secrets.TSCIRCUIT_BOT_GITHUB_TOKEN; this step needs the same treatment to reliably close PRs.
Useful? React with 👍 / 👎.
1 participant
Summary
Testing
https://chatgpt.com/codex/tasks/task_b_68debb98dab0832e927ea1391eb58a53