Sign in

Search issue titles and bodies, change requests and comments. Private repositories you cannot read are not included.

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.

Rewrite the README around the new tagline

e73d453fe4edf2d95ec7e178dad0c232b5ece1c7 · Keenan Nemetz · 2d ago · parent 18c559ea

Rewrite the README around the new tagline

"A forge that lives in your Git repo" replaces "A small but mighty software
forge that lives in your Git repository" everywhere it is the brand line: the
README, the docs index, and the .deb/.rpm description. The built-in landing-page
tagline becomes the same sentence, so a new instance shows it without config.

The package description said CI records live in Git. They live in
data/runs.db, so it now says CI history stays on the instance, and it names
comments, which do live in the vole branch, and says reviews where it used to
say approvals.

The README is the front page and nothing else: the tagline, why the project is
worth using, and links. The quick start, the documentation table, and the
browser sign-in setup move out; the first two are already in the docs, which the
README now links. Development notes move to DEVELOPMENT.md. The private
repository 404 note is dropped because docs/accounts-and-access.md covers it,
and Contributing no longer tells coding agents to read AGENTS.md.

packaging/nfpm.yaml +4−3

@@ -16,10 +16,11 @@ vendor: Rodent Software
16 16 homepage: https://github.com/rodent-software/vole
17 17 license: Apache-2.0
18 18 description: |
19 A small software forge that lives in your Git repository.
19 A forge that lives in your Git repo.
20 20
21 Code, issues, change requests, approvals, releases, and CI records live in Git.
22 One binary, one config file, no extra services to operate.
21 Code, issues, comments, change requests, reviews, and releases live in Git. CI
22 history stays on the instance and is backed up with it. One binary, one config
23 file, no extra services to operate.
23 24 depends:
24 25 # The server shells out to git for every push, clone, and metadata write.
25 26 - git