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.

#172

Make the run list say what triggered each run

merged · by keenan 6d ago · merged into main at 57dc79af by keenan 6d ago

keenan opened this 6d ago

The runs table said only which ref a run used, so a push, an issue event and a manual dispatch looked alike. Each run now has a TriggerTitle — the same words the activity feed uses — and the list shows it in a Triggered by column. The run page uses the same wording in its subtitle.

The separate workflows page is gone. 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. /r/<repo>/workflows now returns 404, the dispatch page’s Cancel returns to the run list, and the docs no longer describe a page that does not exist.

A finished run no longer shows the full live log viewer above its step logs. Each step keeps its own output, and the full log is a Download full log link (?download=1, served as an attachment) rather than a second copy of every step’s output. A run that is still going keeps the live viewer.

Verified with vole workflow run verify (format, vet, build, licenses, govulncheck, packages, markdown links, race tests).

Discussion (0)

No discussion yet.