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.
Require a linked issue when a change request opens
0789f22ea633bf995417893c0052abb6a36d5520 · Keenan Nemetz · 9d ago · parent 1265ea55
Require a linked issue when a change request opens Add a per-repository policy for teams that want every proposed update to trace back to an issue. The browser marks Closes as required, and the pre-receive hook applies the same rule to requests added through the CLI or a hand-written metadata commit. Existing requests stay editable and landable.
docs/change-requests.md +14
| @@ -124,6 +124,20 @@ resolves it when the link is rendered. `closes:` is not where that resolution | |||
| 124 | 124 | lives: it holds ULIDs, because that is the reference that survives a rewritten | |
| 125 | 125 | history. | |
| 126 | 126 | ||
| 127 | A repository can require a linked issue for every new change request. The | ||
| 128 | checkbox is in **Settings → Access**, and the same rule is available to an | ||
| 129 | instance admin from the terminal: | ||
| 130 | |||
| 131 | ```sh | ||
| 132 | vole admin acl require-issues enable demo | ||
| 133 | ``` | ||
| 134 | |||
| 135 | The request page marks **Closes** as required, the browser refuses an unlinked | ||
| 136 | request, and the push gate refuses one added through the CLI or a hand-written | ||
| 137 | metadata commit. Existing requests are unaffected: turning the setting on does | ||
| 138 | not invalidate history, and turning it off allows new requests with no link | ||
| 139 | again. | ||
| 140 | |||
| 127 | 141 | Only an open request may be relinked: a merged request's list records what the | |
| 128 | 142 | merge did, and a closed one is not going to land. The request page's **Issues** | |
| 129 | 143 | section lists the linked issues in the same rows as the overview's recent issues. | |