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.

Number issues and change requests for human references

e05f1c48d4ee55635cd7b77889f0545137198106 · Keenan Nemetz · 13d ago · parent 41d1fee9

Number issues and change requests for human references

A ULID is an unreadable handle, and the 8-character prefix the list showed
is mostly timestamp: this repository's 27 issues shared seven distinct
six-character prefixes and two pairs already collided at eight. The part
people actually type carried almost no information.

Issues and change requests now share one gap-free sequence (#1, #42, ...)
derived from the creation order in the metadata branch's history, the way
one forge counts both in a single run.

The number is not stored. It is the rank of the entity's creation commit,
so nothing is written when an entity is created, a repository needs no
backfill, the same history gives the same numbers on every clone, and
`vole admin index rebuild` reproduces them from git. A ULID stays the
identity: paths, front matter, `closes:` and audit entries are unchanged,
and data/index.db only caches the mapping so a page render does not walk
history.

Every id-taking command accepts a number, `#42` links in a body through a
kind-agnostic /r/<repo>/n/42 route, and --closes resolves an alias to the
ULID before writing.

Closes #45

AGENTS.md +5−1

@@ -15,7 +15,11 @@ This repository uses Vole as its forge, not GitHub. Read
	15	15
	16	16	If `vole` is unavailable or the key is not recognized, stop and ask. Do not
	17	17	guess an author from `git config`.
	18		- Use the full 26-character ULID for issues. Short prefixes can collide.
		18	- Refer to issues and change requests by their `#42` number when reading and
		19	quoting. Use the full 26-character ULID when durability matters (a script, a
		20	commit message) and for `closes:`: numbers are derived from the creation order
		21	in the `vole` branch history, so a rewrite renumbers what came after it, and
		22	ULID short prefixes can collide.
	19	23	- Use `vole issue ...` and `vole change ...` for forge operations. Use SSH Git
	20	24	for code changes.
	21	25	- Run the relevant checks before pushing (`vole workflow check`, then