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.
Phase 3: a change request can be discussed
7c6e52e75f3a33be57a81663bc840edd6e14f7f9 · Keenan Nemetz · 17d ago · parent 3c5d11fa
Phase 3: a change request can be discussed Until now the only ways to say something about a request were editing its body or approving it. A review thread is now a pushed file like everything else: requests/<ulid>/comments/<ulid>.md author + created, then the body It is the *same file shape* as a comment on an issue and is read and written by the same code (`issues.ParseComment`, `issues.RenderComment`, with `requests.Comment` as an alias), so the thread inherited the validation, the markdown boundary and the ownership rule instead of reimplementing them. That last one is the part worth having: `pre-receive` compares the author on the old blob to the pushing account, so a review comment is its author's to edit or delete, an admin may repair a thread (audited), and rewriting the author line in the same push does not launder it. `vole request comment <id> -m` prints the comment's id and the page anchor (`#c-<ulid>`), `edit-comment` and `rm-comment` are the author's own words, and `request show` prints the thread so the ids are discoverable at all — an id nobody can see is an id nobody can use. Adding a comment is free, like adding one to an issue: a new file's author is a claim, and the boundary has never pretended otherwise. The request's own file stays outside the ownership rule, for the reason an issue's does: state, head and base are shared, and updating them is the author's normal edit. Verified: TestParseReadsTheDiscussion (a thread plus an approval in one tree, ordered by id), TestCommentNeedsAnAuthorAndATime and TestUnknownFileInARequestIsRefused (the subtree stays a closed format, with both expected shapes named), TestCommentPaths (a request comment is not an issue comment and not an approval); and end to end through the binary, TestRequestDiscussionIsPushedAndOwned — the empty state prints the command, the CLI adds a comment, the page renders it with its anchor and `request show` lists it, a writer is refused rewriting, adopting and deleting somebody else's comment, may join the thread and may edit his own — with the issue-comment empty state assertion added to TestIssuePushedThenRendered earlier. scripts/ci.sh green (gofmt, vet, build, markdown links, go test -race ./...).
README.md +14
| @@ -250,6 +250,20 @@ merge whose parents are the branch tip and the approved commit. That second shap | |||
| 250 | 250 | `vole request show <id>` prints the same `merge:` line from a clone, and says so when | |
| 251 | 251 | the head is not in the clone rather than guessing. | |
| 252 | 252 | ||
| 253 | A request can be discussed, and the discussion is a normal pushed file — the same | ||
| 254 | shape as a comment on an issue: | ||
| 255 | |||
| 256 | ```sh | ||
| 257 | vole request comment <id> -m "Does this hold for the empty repository case?" | ||
| 258 | vole request comment <id> -m "Good catch, amended." # prints the comment id | ||
| 259 | vole request edit-comment <id> <comment-id> -m "Rephrased." | ||
| 260 | vole request rm-comment <id> <comment-id> | ||
| 261 | ``` | ||
| 262 | |||
| 263 | A comment belongs to whoever wrote it: only that account can change or delete it, | ||
| 264 | and an admin override is audited. The thread shows on the request page with an | ||
| 265 | anchor per comment (`#c-<ulid>`), so a remark can be linked. | ||
| 266 | |||
| 253 | 267 | ```sh | |
| 254 | 268 | vole acl protect demo refs/heads/main # protect a branch | |
| 255 | 269 | vole acl approvals demo 2 # require two approvals (default 1) | |