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.
Create and edit releases from the browser
ec34301375902f6b08c0171bf91b98cbcc55c63c · Keenan Nemetz · 15d ago · parent 09b15120
Create and edit releases from the browser Maintainers get a New release form that writes the same annotated tag the CLI writes: tag name, target commit, and notes become the tag message, with the account as tagger. Edit notes rewrites the tag message only while no artifact is attached, matching the release-immutability rule; lightweight tags and releases with files stay locked. Tag names are validated, existing tags are refused, reserved page names are rejected, and both actions are audited.
docs/releases.md +9
| @@ -24,6 +24,15 @@ tag appears in the release list for completeness, but it has no notes and cannot | |||
| 24 | 24 | carry release files. `vole release create` refuses to overwrite an existing tag | |
| 25 | 25 | and tells you to choose a new name. | |
| 26 | 26 | ||
| 27 | ## Create a release in the browser | ||
| 28 | |||
| 29 | A repository maintainer can create the same annotated tag from **Releases → New | ||
| 30 | release**: choose a tag name, a target branch or commit, and write the notes. The | ||
| 31 | notes become the tag message and the tagger is the account that submitted the | ||
| 32 | form. **Edit notes** changes the message of an annotated tag while the release has | ||
| 33 | no files attached; once an artifact is published the release is immutable, and | ||
| 34 | the web refuses the edit. Lightweight tags are never editable. | ||
| 35 | |||
| 27 | 36 | ## Download source archives | |
| 28 | 37 | ||
| 29 | 38 | The `/r/<repo>/releases` page lists every tag. A release page shows the notes, the | |