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.

Add event, schedule and manual workflow triggers

eb07ff5696e0d83201215966e3ea1e6a24467581 · Keenan Nemetz · 8d ago · parent 1cde8b9e

Add event, schedule and manual workflow triggers

Workflows can now react to change requests, issues, comments, cron
schedules and manual runs, and a push trigger can filter by the paths it
changed. Branch and tag patterns gain ! exclusion.

Event runs are pinned with a JSON payload and the runner exposes it as
VOLE_EVENT, VOLE_EVENT_ACTION and VOLE_EVENT_PATH. Change-request runs
check out the base tip and carry the head and changed files, so an event
never executes an unapproved contributor commit.

Workflow dispatch resolves typed inputs and is available from the
workflows page and `vole workflow dispatch`. Deduplication now includes
an occurrence so the same commit can run for a later event or schedule
slot while a push remains idempotent.

Part of: #138

docs/runner.md +5

@@ -138,6 +138,11 @@ Container defaults are intentionally closed:
	138	138	run it);
	139	139	- the steps run as the runner user's `uid:gid` by default.
	140	140
		141	A run started by a non-push trigger also gets a directory mounted at `/run/vole`
		142	with the pinned event as `event.json`, plus `VOLE_EVENT`, `VOLE_EVENT_ACTION`, and
		143	`VOLE_EVENT_PATH`. The file is data for a step to read; a workflow cannot replace
		144	those variables through `env:`. See [Workflow reference § Event data available to steps](reference/workflow-reference.md#event-data-available-to-steps).
		145
	141	146	The container's own filesystem is writable, and thrown away with the container:
	142	147	nothing a job writes there survives the run, and an unprivileged uid cannot write
	143	148	the image's root-owned paths anyway. What protects the machine is the mount set —