Fossil

“Fossil is very opinionated about some things, in particular, the inability to rewrite history, which makes it a non-option for some.”

“I've been gradually migrating my Git repos to Fossil as I've been touching them. Been quite happy with it.”

“every instance includes those features, this makes the social platform "the web itself"”

“solves this pretty nicely. You can have documentation as files or in a special wiki namespace and it's versioned both ways”

“This prioritises accuracy/history of what happened, but this has significant disadvantages and practically no advantages”

“it has a better log view than git and has better traceability through SQL based search”

“Fossil already offers a million settings. Add another and make me turn on "dangerously-unsafe-rebase" to get the feature if need be.”

“It's a version management system! It's supposed to maintain the history of what's been done, both good and bad.”

“Fossil has no way to fix it, by design, and I find it an absolute showstopper.”

“it's perfect for my needs. Lightweight, has its own integrated web server and forge features should I need them, and it's dead easy to use.”

“fossil bakes in issues and wikis and all that other stuff that makes it hard to use plain git”

“the built-in features are very useful, especially for anyone looking to reduce their dependence on a centralized host”

“fossil‘s simplicity is a breath of fresh air for anyone who has to use git from a CLI”

“would be limited to just providing UI and would be unable to hold our data hostage by design”

“Fossil with its integrated issue management right in the repo is actually a perfect match for the LLM era”

“The user interface, both command and web, is light-years better than anything Git related.”

“packages the entire repository state—code history, wiki, tickets, forum—into a single file”

“which also did handle binary files better than Git when i tested it years ago, though not as good as Subversion or P4”

“it is aggressively hostile to the kind of history rewriting we are used to routinely”

“seems like it could make it much easier for agents to understand and work with the full context of a project”

“The idea is good, but I do not believe that the better technical solution necessarily wins.”

“Fossil gets 90% there with integrating tickets (issues), forums and wikis as part of the repo itself.”

“Fossil is very easy to self host. If you already have a web server it needs maybe 10 or 15 lines of server config.”

“Part of the problem is that fossil is very opinionated. It's great if your development flow is similar to that of the sqlite team.”

“Fossil's internal tools (wiki, forum, tickets , etc) are just so useful to have versioned with your code in one file.”

“Fossil is delightful and definitely nails a feeling of decentralization that I think we ruined completely with git”

“Fossil's implementation is the best, since a cherry-picked commit always points back to its origin.”

“It's nice that unlike git instaweb you don't need to install an additional web server”

“Not only is it a full suite of tools associated with the repository (discussions, tickets, wiki)”

“Fossil is a strong base for this because the repo is already a structured SQLite database with built-in versioning”

“I made Fossil because I've been coding with Claude Code for 6+ months and the same problem keeps showing up in every project.”

“a 3rd party addition doesn't make Git as local-first as Fossil when it comes to other things than source code”

“I like it but the problem is everyone else already knows git and everything integrates with git.”

“I really enjoy how local-first it is, as someone who sometimes work without internet connection.”

“I love fossil and the many features it provides in itself and would use it for everything, except that it doesn't have (working) Intellij plugin”

“Seems like feature creep motivated by the wants of a single project (SQLite).”

“fossil is really cool for the simple fact that you get your issues, PR and wiki all stored in an SQLite DB”

“fossil is much more appealing when you look at the underlying model and how it bundles wiki and issues along with the repository”

“There's no code review system for Fossil, because the SQLite guy doesn't believe in formalized code review.”

“There have been other VCS tools with arguably better UIs and feature sets than Git (Mercurial, Fossil)”