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.

Document where each role may push a change branch

a781cd9b72583eb0a18d875c879cc76873572e5e · Keenan Nemetz · 6d ago · parent ac541b26

Document where each role may push a change branch

The review docs described the contribute account's namespaced branch as if it were the only way to open a change, and one sentence claimed the CLI needed maintain access even though pre-receive lets a contributor file an issue, comment, or open a change from its own branch. Say what each role may push, and keep the namespace rule where it applies.

docs/accounts-and-access.md +3−2

@@ -394,8 +394,9 @@ cannot name a commit they did not push. A maintainer can approve the request, an
	394	394	landing it still goes through the same protected-branch gate.
	395	395
	396	396	The CLI's `vole issue new`, `vole issue comment` and `vole change new` write the
	397		metadata branch directly, so those commands need `maintain`. Contributors use the
	398		web for those actions.
		397	metadata branch directly. Pre-receive checks the same per-path rules as the
		398	browser, so a `contribute` account can use those commands too: it may file an
		399	issue, comment, and open a change from a branch in its own namespace.
	399	400
	400	401	Contributor branches are ordinary branches except for one rule: CI does not run
	401	402	for them automatically. A maintainer or admin opens the change request for the