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.
Document where each role may push a change branch
a781cd9b72583eb0a18d875c879cc76873572e5e · Keenan Nemetz · 6d ago · parent ac541b26
Document where each role may push a change branch The review docs described the contribute account's namespaced branch as if it were the only way to open a change, and one sentence claimed the CLI needed maintain access even though pre-receive lets a contributor file an issue, comment, or open a change from its own branch. Say what each role may push, and keep the namespace rule where it applies.
docs/getting-started.md +2−2
| @@ -68,8 +68,8 @@ vole admin repo create demo --owner you | |||
| 68 | 68 | Creating an account requires its first SSH key: the account and key are written | |
| 69 | 69 | together, so a name is never claimed by an account that cannot sign in. Use | |
| 70 | 70 | `vole admin account add-key` afterwards to attach more keys. The account name is | |
| 71 | permanent — contributor branches live under `refs/heads/contrib/<name>/`. The owner | ||
| 72 | of a new repository is its first admin. | ||
| 71 | permanent — a `contribute` account's branches live under | ||
| 72 | `refs/heads/contrib/<name>/`. The owner of a new repository is its first admin. | ||
| 73 | 73 | ||
| 74 | 74 | New repositories are private. To make the web page and anonymous clone URL | |
| 75 | 75 | readable, publish it: | |