CodeWhale BotandClaude Opus 5.5
59e941a511
Hunter moved the Codewhale repositories to github.com/codewhale-hq on 2026-10-05. Rewrite Hmbown/<moved repo> slugs to codewhale-hq/<repo> in docs, READMEs (all 19), website, CHANGELOGs, workflows, issue templates, Cargo/npm/VS Code/nix/winget metadata, install and updater code, the bundled first-party marketplace catalog and their tests: 1,795 references in 434 files, plus four escaped regex literals. Docker images publish to ghcr.io/codewhale-hq/codewhale from the next release. Old URLs keep working through GitHub's transfer redirects (verified live: API releases/latest, HTML releases/latest, release asset downloads, codeload tarballs, git clone), so released clients keep updating. Left unchanged on purpose: Hmbown/codewhale-cu-plugin (not moved yet; its shipped updater refuses redirects), Hmbown/deepseek-skills, cwc and other repos that did not move; package identities (winget Hmbown.CodeWhale, NSIS publisher); vendor/codewhale-ratatui (frozen reviewed package); and the extension-host GitHub adapter with tools/github/report.rs and their parity fixture, which need a bundle rebuild and move together in a follow-up. README translation stamps updated to the new README.md hash. Validation: npm test (wrapper 101/0, SDK 19/0, extension host 398 passed / 0 failed / 7 skipped, web 763/0) and npm run check:web exit 0 (one pre-existing facts-lib.mjs lint warning). cargo check --workspace --tests --all-features --locked: exit 0. cargo test -p codewhale-cli -p codewhale-release -p codewhale-protocol and the touched codewhale-tui modules (client, cloud_dispatch, commands, dispatch_runner, llm_client::mock, oauth, operate, plugins::marketplace, remote_control, remote_setup, tools::mcp_registry, tools::web::fetch, working_set, tui::ui::tests): all ok, 0 failed. check-readme-translations (18 in sync), readme locales, TUI locale parity, product vocabulary, web locales, contributor credit, plugin claims, release-workflows.test.js and check-versions all pass. Co-Authored-By: Claude Opus 5.5 <[email protected]> Signed-off-by: CodeWhale Bot <[email protected]>
2.7 KiB
Issue Triage
Triage aims issues at the agent-ready standard defined in
the agent-ready issue standard (codewhale-ops): bodies that a fresh agent
can execute without extra context. This page covers the stale/needs-info
lifecycle that runs alongside that standard.
Stale needs-info cleanup
The stale workflow only acts on issues that a maintainer has explicitly labeled
needs-info. This keeps old roadmap, release, security, and current milestone
work out of automatic cleanup unless a maintainer first marks the issue as
waiting on reporter input.
Required labels:
needs-info: waiting on reporter information or current-version reproduction details.stale: inactiveneeds-infoissue pending automatic closure.keep-open: protected because maintainers intentionally keep it open.pinned: protected maintainer issue.
Protected labels for stale cleanup:
pinnedkeep-openrelease-blockersecurity
A bug issue is not protected just because it is a bug. If a maintainer has
also labeled it needs-info, it is eligible for stale warning and closure
unless one of the protected labels above is present.
Dry-run queries
Run these before changing stale policy or doing a manual cleanup pass:
STALE_CUTOFF=$(python3 -c 'from datetime import date, timedelta; print(date.today() - timedelta(days=45))')
NEEDS_INFO_CUTOFF=$(python3 -c 'from datetime import date, timedelta; print(date.today() - timedelta(days=30))')
gh issue list --repo codewhale-hq/CodeWhale --state open \
--search "updated:<${STALE_CUTOFF}" \
--limit 100 \
--json number,title,updatedAt,labels,url
gh issue list --repo codewhale-hq/CodeWhale --state open \
--search "label:needs-info updated:<${NEEDS_INFO_CUTOFF}" \
--limit 100 \
--json number,title,updatedAt,labels,url
gh issue list --repo codewhale-hq/CodeWhale --state open \
--search "created:<${STALE_CUTOFF} comments:0 -label:keep-open -label:release-blocker -label:security" \
--limit 100 \
--json number,title,createdAt,updatedAt,labels,url
Use updatedAt, labels, and current release relevance as the closure basis.
Creation date alone is too aggressive.
First cleanup pass
Before relying on automation, perform one manual pass:
- Label unresolved old bug reports as
needs-infoonly after asking for current-version reproduction details. - Close obvious GUI, VS Code, and web UI duplicates with links to canonical desktop/runtime issues.
- Close old brand-discussion issues as superseded when the Codewhale rebrand and README/history work already covers them.
- Protect intentional v0.9.0 roadmap shards with
keep-openor close them as superseded by a canonical epic.
Do not close release blockers, security issues, or active milestone work from stale automation alone.