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.

Search for an issue when linking it to a change

838f282eebf7e68f61318eae93d03263df1341df · Keenan Nemetz · 10d ago · parent 267feec2

Search for an issue when linking it to a change

The link field only accepted an id that the author already knew. It is now a search box over the issue index that matches a title, a #number, or a ULID prefix. A matching issue is a button: picking one posts the same link write and replaces the Issues section with the new list. Issues already linked are left out of the results.

docs/change-requests.md +6−6

@@ -121,12 +121,12 @@ history.
	121	121
	122	122	Only an open request may be relinked: a merged request's list records what the
	123	123	merge did, and a closed one is not going to land. The request page's Issues
	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
	128		issue; linking one does not, and a request that is closed without landing leaves
	129		its issues open.
		124	section lists the linked issues in the same rows as the overview's recent issues.
		125	Its search box finds issues by title, `#number`, or ULID; picking a result links
		126	it, and the unlink icon removes one. Both controls use the same `closes` list as
		127	the CLI, and only the request's author or a maintainer may change it. Landing is
		128	what closes an issue; linking one does not, and a request that is closed without
		129	landing leaves its issues open.
	130	130
	131	131	## How approvals work
	132	132