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.

Tighten up the issue and change review pages

564acd4b6de233740f3c19e297c4655e8952d40c · Keenan Nemetz · 15d ago · parent a464f892

Tighten up the issue and change review pages

- Move contributor-branch CI approval from the Runs tab to the change
  request header, and return the allow form to that request.
- Put issue and change actions in the page header, right aligned with the
  title, instead of duplicating them in the sidebar.
- Drop sidebar details that repeated the header: state, author, age and
  reference. Keep labels, assignees, review base/head, approvals and checks.
- Consolidate approval status into one section and remove the empty-state
  line now covered by the count.
- Fix diff row spacing: keep pre-wrap on the code column only, so template
  whitespace in the gutter cells no longer creates blank lines.

Update the contributor CI test, the HTMX fragment expectations and the
documentation that named the Runs tab as the approval location.

docs/workflows.md +1−1

@@ -110,7 +110,7 @@ mutable tag changes what a build means.
	110	110	A push to `refs/heads/contrib/<name>/...` queues no work by itself. Those
	111	111	branches contain code from outside the project's maintainer group, and running a
	112	112	workflow executes it on a runner. CI is held until a maintainer or admin opens the
	113		Runs tab and chooses Allow CI for this tip next to the contributor branch.
		113	change request for the branch and chooses Allow CI for this tip there.
	114	114
	115	115	The approval is keyed by the exact commit, not by the branch. A new commit or a
	116	116	force-push is a new decision, so the contributor cannot push once and inherit