Files

Tom Boucher 2a915c1b82 chore: migrate references from gsd-build to open-gsd/get-shit-done-redux (#120 ) (#121 )

Security-motivated migration of all stale repository and npm-scope references.

Three categories of changes (58 files, 174 substitutions):

1. gsd-build → open-gsd (security-critical):
   - .github/workflows/release-sdk.yml — npm token comment, tarball filename pattern
   - .github/workflows/hotfix.yml — same
   - .changeset/fix-3406-detect-stale-sdk-shadow.md — @gsd-build/sdk → @open-gsd/sdk
   - .changeset/sharp-quails-leap.md — same
   - get-shit-done/workflows/update.md — CHANGELOG raw GitHub URL

2. GSD-redux org slug → open-gsd (canonical rename):
   - package.json + sdk/package.json — repository/homepage/bugs metadata
   - All README.*.md — live badge and link sections
   - CONTRIBUTING.md, CONTEXT.md, QUICK-WINS-CONFIRMED-BUGS.md
   - .coderabbit.yaml, .release-monitor.sh, scripts/sync-rulesets.sh
   - docs/** — all live agent/ADR/user-facing documentation
   - tests/** — repo slug assertions and test fixtures
   - scripts/changeset/cli.cjs + github-release-notes.cjs
   - .github/ISSUE_TEMPLATE/*, .github/pull_request_template.md
   - bin/install.js, get-shit-done/bin/lib/model-catalog.cjs
   - sdk/HANDOVER-*.md, sdk/src/*.test.ts

3. CLAUDE.md (gitignored local file — not in this commit):
   Updated separately outside git: --repo gsd-build/get-shit-done →
   --repo open-gsd/get-shit-done-redux with security warning.

Intentionally unchanged: CHANGELOG.md, docs/RELEASE-*.md,
.changeset/README.md, .changeset/build-hooks-atomic-write.md,
README.md migration table (historical fork record),
tests/changeset-serialize.test.cjs line 78 (serialization fixture).

The gsd-build/get-shit-done repo is compromised (rug-pull documented in
README.md). Do not push to or interact with that repo.

Closes #120

2026-05-22 12:28:16 -04:00

1.7 KiB

Raw Blame History

Triage Labels

Maps the five canonical triage roles to the actual label strings in open-gsd/get-shit-done-redux.

Canonical role	Label in this repo	Notes
`needs-triage`	`needs-triage`	Auto-applied by GitHub Action on every new issue
`needs-info`	`needs-reproduction`	Waiting on reporter — cannot reproduce, more info required
`ready-for-agent`	`confirmed`	Bug verified + fully specified — AFK agent can pick up
`ready-for-human`	`approved-enhancement` / `approved-feature`	Enhancement/feature approved by maintainer — human codes it
`wontfix`	`wontfix`	Will not be actioned

Notes on this repo's label model

confirmed is the AFK-agent-ready signal for bugs. It means "verified to exist and reproducible."
For enhancements and features, maintainer approval is approved-enhancement / approved-feature respectively. A contributor (human or agent) may not write code until one of these is applied.
There is no separate "ready-for-human" vs "ready-for-agent" distinction for enhancements — both flow through the same approved-* labels. If the work requires human judgment (design decisions, external access), note it in the issue body.
needs-triage is removed when any other state label is applied.
needs-reproduction is used instead of the generic needs-info — be specific in triage comments about what reproduction steps or information are missing.

1.7 KiB Raw Blame History

Triage Labels

Notes on this repo's label model

1.7 KiB

Raw Blame History