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.

Split repository settings into tabs

e189a23e457b6aa01a35a4586586713cdc2d426d · Keenan Nemetz · 23h ago · parent 87ebcc5a

Split repository settings into tabs

One page held four audiences and ten forms. Each part is now its own tab:
General for the repository's own fields, Access for the instance-admin
rules, Secrets for the values jobs read, and Danger for rename and delete.
A tab is offered only to the accounts that may use it, and a viewer with one
tab gets no row at all. The Access and Secrets tabs, and the failures on
each, keep their own URLs so a redirect and an error land where the form was;
the Access and Secrets fragments survive as deep links.

docs/accounts-and-access.md +7−4

@@ -322,16 +322,19 @@ vole admin acl set-default-role demo read
	322	322	A repository admin can also change the description, default branch, and
	323	323	visibility, and rename or delete the repository, from its Settings tab in
	324	324	the browser. An instance admin has those rights on every repository too.
	325		Visibility
		325	Settings is split into tabs: General (the repository's own fields),
		326	Access (the instance-admin rules), Secrets, and Danger (rename and
		327	delete). Each tab is offered only to the accounts that may use it, and a viewer
		328	who can use one of them sees no row at all. Visibility
	326	329	toggles the default role between `none` and `read`; explicit role entries are
	327	330	left alone. The Accounts table shows only accounts with an explicit role or
	328	331	runner entry; use Add account below it to grant another account a
	329	332	repository-specific role. Access rules and review policy remain instance-admin
	330		operations: instance admins can edit them on the repository's Settings tab,
		333	operations: instance admins can edit them on the repository's Access tab,
	331	334	or with `vole admin acl`.
	332	335
	333		A maintainer who is not an admin also opens that tab, for one section: the
	334		repository's secrets. Values a repository keeps out of its code — a deploy key, a
		336	A maintainer who is not an admin also opens the page, and its one tab is
		337	Secrets. Values a repository keeps out of its code — a deploy key, a
	335	338	registry token, a staging password — belong to the accounts that approve work and allow CI,
	336	339	so the page shows them the names, versions and read times, and the form that sets
	337	340	them. It never shows a value; `vole secret get` prints one when somebody needs it.