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.
Give every account a profile page and a directory of accounts
a6b42433c087ab0c936e34a1d05cf488db7a92d6 · Keenan Nemetz · 8d ago · parent 727df386
Give every account a profile page and a directory of accounts Clicking a name now opens /u/<name>: the issues and changes somebody opened, the reviews they gave, the comments they left, and the repositories that work is in. The numbers and the feed are grouped reads of the same event rows the activity feed pages through, so a profile cannot disagree with the feed, and every read is limited to the repositories the reader may open. A private repository's work is not a number an outsider gets to learn, so two readers can see different totals and the page says what its numbers cover. /u lists the roster. Account names are public on this instance; their activity is not. Both pages ask crawlers to leave them out of an index. @name in an issue, a comment, a change request, or a release note links to the account it addresses, using the mention scanner CI already evaluates: what reads as an address on the page is what a workflow sees. A name that is not an account stays text, and code samples are skipped. Git author names are not linked and commit counts are not shown. A commit author is a name somebody typed, not the credential that proves an account, and the index only keeps the top eight authors of each default branch anyway.
docs/issues.md +4
| @@ -143,6 +143,10 @@ vole issue new --title "the docs page is blank" \ | |||
| 143 | 143 | the change request that holds the number. `#<ulid>` links by id and is the form | |
| 144 | 144 | that keeps working if history is ever rewritten. Commits that mention an id are | |
| 145 | 145 | shown as backlinks on the issue page. | |
| 146 | - Writing `@name` links to that account's profile. It is the same syntax a | ||
| 147 | workflow's `mentioned` filter matches, so the page and a job agree about who was | ||
| 148 | addressed. Code samples are skipped, and a name that is not an account stays | ||
| 149 | text. | ||
| 146 | 150 | - An assignee must be a valid account name: lowercase letters, digits, `-`, and | |
| 147 | 151 | `_`. The name is stored as written because account names are never reused. A | |
| 148 | 152 | value that is not an account name cannot be an assignee. | |