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.

Make the run list say what triggered each run

57dc79afa8097830de03fc2fc2c19561470b6d36 · Keenan Nemetz · 6d ago · parent 338a19dd

Make the run list say what triggered each run

The runs table said only which ref a run used, so a push, an issue event
and a manual dispatch looked alike. Give each run a TriggerTitle and show
it in a "Triggered by" column; the run page uses the same words.

Drop the separate workflows page. The run list is where a job is found,
and the run page now links the workflow definition it ran, so a second
page listing the same jobs only split the answer.

Show the full log viewer only while a run is going. A finished run has
per-step logs, and the full log is a download rather than a second copy
of every step's output.

server/web/static/vole.css +3−2

@@ -1605,8 +1605,9 @@ details[open] > summary .tree-chevron { transform: rotate(90deg); }
	1605	1605
	1606	1606	/* ---------- run detail ---------- */
	1607	1607
	1608		/* A run's summary is four facts, not a paragraph: how long it took, how long it
	1609		waited, what it ran on, and which commit it tested. */
		1608	/* A run's summary is a row of facts, not a paragraph: how long it took, how
		1609	long it waited, what it ran on, which commit it tested, and the workflow
		1610	definition it ran. */
	1610	1611	.run-summary {
	1611	1612	display: grid;
	1612	1613	grid-template-columns: repeat(auto-fit, minmax(11rem, 1fr));