Skip to content

fix: nextjs-tracker agent hangs because it uses wrong repo name #691

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
southpolesteve merged 1 commit into from
Mar 26, 2026
+4 −2
Merged

fix: nextjs-tracker agent hangs because it uses wrong repo name #691

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions .opencode/agents/nextjs-tracker.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,11 +42,13 @@ A commit is relevant if it touches anything that vinext reimplements or relies o

## How to work

**Important:** All `gh issue` commands MUST use `--repo "$GITHUB_REPOSITORY"` so they target the correct repo. The `GITHUB_REPOSITORY` environment variable is set by the CI workflow (e.g., `cloudflare/vinext`). Never guess the repo name.

1. Read through all commits provided. For each one, fetch the full diff using `gh api` if the summary is ambiguous.
2. Classify each commit: relevant or not. If not, skip it.
3. For relevant commits, group closely related commits (e.g., 3 commits all part of one feature) into a single issue rather than opening one issue per commit.
4. Before opening any issue, check for duplicates: run `gh issue list --label "nextjs-tracking" --state open --limit 50` and search for the feature/area name. If a matching open issue already exists, skip it.
5. Open one GitHub issue per distinct relevant change using the format below.
4. Before opening any issue, check for duplicates: run `gh issue list --repo "$GITHUB_REPOSITORY" --label "nextjs-tracking" --state open --limit 50` and search for the feature/area name. If a matching open issue already exists, skip it.
5. Open one GitHub issue per distinct relevant change using the format below. Always pass `--repo "$GITHUB_REPOSITORY"` when creating issues.
6. If nothing is relevant, do nothing. Do not open an issue to say "nothing relevant today."

## Issue format
Expand Down
Loading