Why
“Change request” is a heavy name for what the UI already calls “Changes” on the detail page. “Changes” is the easier concept: a branch proposed for a base branch. Use one word in the web UI.
Scope
- Repository tab and page title:
Change requests→Changes. - New/open controls:
New change request/Open change request→New change/Open change. - List, empty states, overview sidebar, home page, activity chips, and activity feed details.
- Add the missing subtitle to the changes list page.
- Keep route names, metadata layout, and internal identifiers unchanged.
Acceptance criteria
- No user-facing web label says “Change request(s)”; the top-level tab and page heading are “Changes”.
- The changes list page has a one-line subtitle like the other repository pages.
- Tests that assert the old labels are updated.
gofmt,go vet ./..., andgo test ./server/...pass.