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.

docs/workflows.md +6−6

@@ -37,10 +37,10 @@ jobs:
	37	37	```
	38	38
	39	39	`name` and `description` say what the workflow is for; the file path stays its
	40		identity. When `name` is absent, the workflows page shows the file's base name
	41		(`verify.yaml` becomes `verify`). A job's `name` is shown in place of its ID on the
	42		workflows and run pages. These fields are display metadata: they do not change
	43		what runs, and two workflows may share a name.
		40	identity. When `name` is absent, a run shows the file's base name (`verify.yaml`
		41	becomes `verify`). A job's `name` is shown in place of its ID on the run page.
		42	These fields are display metadata: they do not change what runs, and two
		43	workflows may share a name.
	44	44
	45	45	Every job must name the environment it runs in, with exactly one of `image:` or
	46	46	`image-file:`. A workflow that names neither fails the push that introduced it.
@@ -209,8 +209,8 @@ the agent's instructions from the repository, never from the event body.
	209	209
	210	210	## Manual runs
	211	211
	212		A workflow with `on.workflow-dispatch` gets a Run workflow button on the
	213		workflows page. Maintainers and instance admins can also start one from a clone:
		212	A workflow with `on.workflow-dispatch` can be started by hand. Maintainers and
		213	instance admins can start one from a clone:
	214	214
	215	215	```sh
	216	216	vole workflow dispatch --workflow .vole/workflows/deploy.yaml \