Skip to content

docs(specs): repoint short references under the tracker's old name #18

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
StoneyJackson merged 1 commit into from
Oct 27, 2026
Merged

docs(specs): repoint short references under the tracker's old name #18

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
7 changes: 7 additions & 0 deletions dev-docs/specs/2026-10-13-change-requests-split-design.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
Loading