Sign in

Search issue titles and bodies, change requests and comments. Private repositories you cannot read are not included.
vole
Clone

Read only, no credentials:

https://rodent.software/git/vole.git

Write over SSH with a registered key:

git clone ssh://git@0.0.0.0:2222/vole.git

A free and open-source forge that lives in your Git repo.

#74

Rename Change requests to Changes in the web UI

merged · by keenan 11d ago · merged into main at db5e4382 by keenan 11d ago

keenan opened this 11d ago

Summary

Use “Changes” as the web UI name for a proposed branch update. “Change request” is a heavier name for the same idea, and the detail page already called the diff tab “Changes”.

  • Repository tab and list heading are now Changes.
  • New/open controls are New change and Open change.
  • Overview sidebar, home page, activity chips and feed details, empty states, page titles, and permission errors use the same word.
  • The changes list page gets the subtitle it was missing: “Branches proposed for a base branch, with review and approvals before they land.”

Routes (/requests), metadata layout (requests/<ulid>/request.md), and Go identifiers are unchanged.

Testing

  • ./vole workflow check
  • go vet ./...
  • go test ./...

Closes #73

Discussion (1)

keenan 11d ago

Follow-up after review: the first subtitle described the data model (“branches”, “base branch”, “land”) rather than what the page is for. It now reads:

Proposed updates to the project, reviewed and approved before they are merged.

The New change page says the same in prose (“Suggest an update to the project. Someone will review it before it is merged”), and the Issues list now has the subtitle it was missing.

To keep this from recurring, I added a Copy section to AGENTS.md with plain-language rules and before/after examples. A test now checks that every repository tab page keeps a page subtitle.