From 93fe173f3a3e223927cb3f7d9d205a285dd27900 Mon Sep 17 00:00:00 2001 From: Stoney Jackson Date: Tue, 27 Oct 2026 17:44:38 +0000 Subject: [PATCH] docs(specs): repoint short references under the tracker's old name ourPLCC/change-requests#N means dev's issue or PR today and the new repo's after the split; the link search must catch these too, including in completed CRs the CLI cannot edit. Co-Authored-By: Claude Opus 5.5 --- dev-docs/specs/2026-10-13-change-requests-split-design.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/dev-docs/specs/2026-10-13-change-requests-split-design.md b/dev-docs/specs/2026-10-13-change-requests-split-design.md index 28c2a88..3711ac2 100644 --- a/dev-docs/specs/2026-10-13-change-requests-split-design.md +++ b/dev-docs/specs/2026-10-13-change-requests-split-design.md @@ -187,6 +187,13 @@ Creating `ourPLCC/change-requests` ends GitHub's redirect from that name to creating the repo, search GitHub for `ourPLCC/change-requests` across the org's code, issues, and pull requests, and repoint each hit at `ourPLCC/dev`. +- **Point at the wrong thing:** short references under the old name, + `ourPLCC/change-requests#N`, which today mean `dev`'s issue or pull request + `N` and afterwards mean `change-requests`'. They hide in the tracker data + too, which moves to the new repo. Search for them with the URLs, and with + `grep -rn 'change-requests#[0-9]' backlog/` in `dev`, and rewrite each to + `ourPLCC/dev#N`. The CLI cannot edit a CR in `backlog/completed/`, so a + hit there is the one tracker edit made by hand. - **Clones whose `origin` uses the old name** (a host `../dev` cloned before the rename) would fetch the new repo. The rewritten hashes make a pull there fail on unrelated histories rather than delete `dev`'s files; the cutover