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.
Build out change review and threaded discussions
f6f4b1db24292d1df877680714952a9c568e2b78 · Keenan Nemetz · 15d ago · parent 564acd4b
Build out change review and threaded discussions - Add Conversation, Files and Runs tabs to change requests. Files uses the code-browser shape with a changed-file tree and one selected-file diff; Runs lists the head commit's workflow results. - Show anchored review comments beneath the line, with a collapsed excerpt read from the exact blob that was reviewed, and return posted anchors to their line note. - Add comment threads: any comment can be replied to, the UI flattens the descendants under one root, reply context links back to the parent, and reply targets feed a single composer at the foot of the discussion. - Collapse reply groups while keeping the root visible, and scroll to the composer when Reply is selected. - Add comment context menus with Reply, Copy text, Copy link, Edit and Delete. Add web edit/delete routes with author or admin checks; deletion leaves a tombstone so replies keep their thread. - Support --reply-to in the issue and change CLI commands, and treat a missing parent as a tombstone rather than an invalid tree. - Fix the diff comment gutter, action button colours, reply labels, and keep the Files tree and diff pane aligned. Update metadata validation, web templates, CSS, JavaScript, tests, and the CLI/change-request/issue docs.
docs/workflows.md +1−1
| @@ -110,7 +110,7 @@ mutable tag changes what a build means. | |||
| 110 | 110 | A push to `refs/heads/contrib/<name>/...` queues no work by itself. Those | |
| 111 | 111 | branches contain code from outside the project's maintainer group, and running a | |
| 112 | 112 | workflow executes it on a runner. CI is held until a maintainer or admin opens the | |
| 113 | change request for the branch and chooses **Allow CI for this tip** there. | ||
| 113 | change request for the branch and chooses **Allow CI** there. | ||
| 114 | 114 | ||
| 115 | 115 | The approval is keyed by the exact commit, not by the branch. A new commit or a | |
| 116 | 116 | force-push is a new decision, so the contributor cannot push once and inherit | |