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.

Say that bridge is a mode, not a mechanism

629fdd87ba637a5b9ea6bfa9960b40445d979911 · Keenan Nemetz · 6d ago · parent d7958024

Say that bridge is a mode, not a mechanism

The reference named the two values without saying why they are those two. Every
supported runtime takes none and bridge for --network, so the field is portable;
what the network is underneath differs by backend, and that is the runner's
business rather than the workflow's.

Part of #160.

docs/reference/workflow-reference.md +6

@@ -529,6 +529,12 @@ to reach out then fails to resolve a host, which is the answer a job that does n
	529	529	need the network should get. Only these two values are accepted; there is no
	530	530	`host`, because a job that shares the runner's network is not isolated from it.
	531	531
		532	Both names are the modes every supported runtime takes for `--network`, so the same
		533	workflow means the same thing on Docker, rootless Podman, and nerdctl. What the
		534	network is underneath differs — Docker's own bridge, Podman's userspace stack,
		535	nerdctl's CNI bridge — and that is the machine's business: the field says whether a
		536	job may reach out, not how the runner provides the route.
		537
	532	538	The job decides, and the machine's own setting fills in only when the field is
	533	539	absent:
	534	540