Fix #339: ssh-keys lane carve-out #351
No reviewers
Labels
No labels
actions
bug
cli
duplicate
enhancement
fork
forum
git storage
help wanted
insights
invalid
issues
moderation
oidc
ownership transfer
packages
pr/merge protection rules
projects
pull requests
question
releases
sponsorships
tags
webhooks
wiki
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
crueber/walhub!351
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/issue-339"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Docs-only: amends docs/go/07_api.md §3 lane note to carve self-service ssh-keys (GET/POST/DELETE /api/v1/ssh-keys) out as token-lane-only, plus a Decisions entry (law 12).
Why carve-out over twins: grep over the repo finds zero references to api-browser/v1/ssh-keys; the only consumer (web/src/pages/Keys.jsx) fetches /api/v1 directly, and 17_ssh.md §3 + 11_config_cli.md name only the /api/v1 routes. Twins would widen the browser-lane surface for no consumer.
Verification: internal/api/routes.go confirms twins absent for ssh-keys and present for every other NonRepo core route (me, owners, owners/detailed, ownerRepos, repos/detailed, profile GET/PUT; instance is services-only by design; discovery served on both lane roots). Feature ExtraRoutes surfaces (repoimport, pulls, mirror, notify, identity, social) all carry both-lane twins. No code changed, no tests affected.
Closes #339.