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.

Store changes under changes/<ulid>/change.md

b492b557f5cc5633b3dcb21fdbb5e2ad98d0bc16 · Keenan Nemetz · 3d ago · parent 9bce3723

Store changes under changes/<ulid>/change.md

The web, the CLI, and the docs call these items changes; only the metadata
tree still said requests. Rename the directory and the record file so the
format and the product use one word.

The tree is a contract, so this is a format change rather than a display
change: the top-level layout stays closed, and a request path no longer
validates. An existing repository is migrated by rewriting its vole branch,
which is an audited admin force-push; the index rebuilds from the new tip
and the #N aliases keep their ULIDs because the rewrite preserves commit
order.

Refs #202 (01M6S3JC3Y2KA6EFJK6APX7A1T).

docs/issues.md +1−1

@@ -142,7 +142,7 @@ vole issue new --title "the docs page is blank" \
	142	142
	143	143	## Rules
	144	144
	145		- Issues and comments live under `issues/` and `requests/` on the `vole` branch.
		145	- Issues and comments live under `issues/` and `changes/` on the `vole` branch.
	146	146	Other paths are rejected. Releases have their own paths, written by Vole. CI
	147	147	records are not stored on the branch; they live in `data/runs.db`.
	148	148	- History on the `vole` branch must be linear. Merge commits are not allowed.