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.

Turn the user directory into a sortable table

4739664b94c4321b83a2650a3a2486ec090aed64 · Keenan Nemetz · 7d ago · parent c14588ef

Turn the user directory into a sortable table

The list became a table with the same counts, and the column headers
order it: user, repositories, issues, changes, reviews, joining date.
Counts start largest-first and the name A to Z; clicking the active
header flips it. The active column carries aria-sort and an arrow.

The search, the status chips (everyone, active, no longer active), the
order and the page all live in the URL and are carried into every link,
so a view can be bookmarked and paging cannot change the question. It is
all server-side, so it works without JavaScript.

Sorting by a count needs every matched account's summary before the page
is cut, so the index now answers for the whole directory in one grouped
query — ActorSummaries — instead of a lookup for a page of names. That
also drops the per-request name list, so a large roster cannot run into
SQLite's bound-variable limit.

Retired accounts are marked in their row and can be filtered to rather
than living in a separate group, and a roster larger than one page is
covered by a test.

docs/accounts-and-access.md +6

@@ -29,6 +29,12 @@ commented on, and the repositories that work is in. Retiring an account keeps it
	29	29	page, marked as no longer active, because every closed issue and merged change
	30	30	still refers to the name.
	31	31
		32	The directory is a table of every account and its visible counts. Search it by
		33	name, narrow it to active or retired accounts, and order it from a column header
		34	— by name, repositories, issues, changes, reviews or joining date. The search, the
		35	filter, the order and the page are all in the URL, so a view can be linked and
		36	paging cannot change the question.
		37
	32	38	What a profile counts is not public. Every number and every event is limited to
	33	39	the repositories the reader may open, so two people can see different totals for
	34	40	the same account, and a private repository's work contributes nothing to a