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/vole.git

Write over SSH with a registered key:

git clone ssh://git@rodent.software: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/reference/workflow-reference.md +7−9

@@ -42,7 +42,7 @@ Unknown keys are rejected. A workflow is validated when it is pushed and again b
42 42 | Field | Type | Required | Default | Meaning |
43 43 |---|---|---|---|---|
44 44 | `version` | integer | yes | — | Schema version. Must be `1`. |
45 | `name` | string | no | the workflow file's base name | Display name on the workflows and run pages. |
45 | `name` | string | no | the workflow file's base name | Display name on the run page. |
46 46 | `description` | string | no | none | One-line summary of what the workflow is for. |
47 47 | `on` | mapping | no | — | Trigger configuration. |
48 48 | `on.push.branches` | list of strings | no | `["*"]` for a workflow with no other trigger | Branch patterns that trigger the workflow. |
@@ -76,7 +76,7 @@ version: 1
76 76
77 77 A display name for the workflow. The file path stays the identity — it is what a
78 78 run records and what `vole workflow run` selects — while `name` is what a reader
79 sees on the workflows and run pages:
79 sees on a run page:
80 80
81 81 ```yaml
82 82 name: Verify main
@@ -90,8 +90,8 @@ metadata; two workflows may share a name.
90 90
91 91 ### `description`
92 92
93 A one-line summary of what the workflow is for, shown under its name on the
94 workflows page and on each run page:
93 A one-line summary of what the workflow is for, shown under its name on each
94 run page:
95 95
96 96 ```yaml
97 97 description: Build, test and lint every push to main.
@@ -335,8 +335,7 @@ a server that was not running for a slot does not replay it later.
335 335
336 336 ### `on.workflow-dispatch`
337 337
338 Marks a workflow as runnable by hand. The browser shows a **Run workflow** button
339 on the workflows page, and the CLI has `vole workflow dispatch`.
338 Marks a workflow as runnable by hand. The CLI has `vole workflow dispatch`.
340 339
341 340 ```yaml
342 341 on:
@@ -406,7 +405,7 @@ letter. At least one job is required.
406 405
407 406 | Field | Type | Required | Default | Meaning |
408 407 |---|---|---|---|---|
409 | `name` | string | no | the job ID | Display name on the workflows and run pages. |
408 | `name` | string | no | the job ID | Display name on the run page. |
410 409 | `description` | string | no | none | One-line summary of what the job does. |
411 410 | `image` | string | one of `image` / `image-file` | — | Registry image the job runs in. |
412 411 | `image-file` | string | one of `image` / `image-file` | — | Name of a definition under `.vole/images/`. |
@@ -425,8 +424,7 @@ neither, is an error.
425 424
426 425 ### `name`
427 426
428 A display name for the job, shown on the workflows page and on the run page in
429 place of the job ID:
427 A display name for the job, shown on the run page in place of the job ID:
430 428
431 429 ```yaml
432 430 jobs: