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.

List a change's linked issues in a Details section

cad93cfe2b6d4ed4c3ed5a1431af4ecb194484ce · Keenan Nemetz · 10d ago · parent 5c22953e

List a change's linked issues in a Details section

The conversation sidebar showed linked issues as one comma-separated line, so there was no way to see what each link was or change it without the CLI. The Details section lists them with the same rows the overview uses for recent issues, and the change's author or a maintainer can link another issue or remove one while it is open. Both controls go through SetRequestCloses, so the browser and 'vole change update --closes' write the same metadata.

docs/change-requests.md +5−1

@@ -120,7 +120,11 @@ lives: it holds ULIDs, because that is the reference that survives a rewritten
	120	120	history.
	121	121
	122	122	Only an open request may be relinked: a merged request's list records what the
	123		merge did, and a closed one is not going to land. Landing is what closes an
		123	merge did, and a closed one is not going to land. The request page's Details
		124	section lists the linked issues in the same rows as the overview's recent issues;
		125	its author or a maintainer can link another issue or remove one there while the
		126	request is open. The input takes the same number or id as the CLI, and the
		127	result is the same `closes` list. Landing is what closes an
	124	128	issue; linking one does not, and a request that is closed without landing leaves
	125	129	its issues open.
	126	130