docs: land the repo-targeting map, ADR 0059, and the rename probe #883

New issue

Open

opened 2026-10-23 04:35:45 +00:00 by hexajon · 0 comments

hexajon commented

2026-10-23 04:35:45 +00:00

Owner

The branch for #685 holds three pieces of work that are done but not merged:

docs/decisions/0059-one-repo-setting-names-a-forge-repo.md, a proposed record: repo= names a forge repo with one meaning on every tool, a bare name means the logged-in user's repo, and dir= stays the folder;
docs/design/repo-targeting-map.md, the map of how each tool picks its repo, host, and login today, with every conflict between the records and the code;
internal/testforge/renameprobe, a forge test that shows how Forgejo and Gitea answer the old path of a renamed or moved repo (every request gets a 301 to the new name on the same host).

No other doc links to the map, so the orphaned-doc test fails.

Acceptance criteria

An existing doc links to the map, so the orphaned-doc test passes.
The decisions index lists docs/decisions/0059 once, after a rebase onto the current main.
The rename probe passes in the forge VM at the baseline and latest pins.
The gate passes, and the branch merges under this issue's number.

The branch for #685 holds three pieces of work that are done but not merged: - docs/decisions/0059-one-repo-setting-names-a-forge-repo.md, a proposed record: `repo=` names a forge repo with one meaning on every tool, a bare name means the logged-in user's repo, and `dir=` stays the folder; - docs/design/repo-targeting-map.md, the map of how each tool picks its repo, host, and login today, with every conflict between the records and the code; - internal/testforge/renameprobe, a forge test that shows how Forgejo and Gitea answer the old path of a renamed or moved repo (every request gets a 301 to the new name on the same host). No other doc links to the map, so the orphaned-doc test fails. ## Acceptance criteria - [ ] An existing doc links to the map, so the orphaned-doc test passes. - [ ] The decisions index lists docs/decisions/0059 once, after a rebase onto the current main. - [ ] The rename probe passes in the forge VM at the baseline and latest pins. - [ ] The gate passes, and the branch merges under this issue's number.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

sixfold-space/madtea#883

No description provided.

Rows
Columns