A fast, native Git history browser you launch from your terminal. Press one command inside a repository and get the useful half of SourceTree: the commit graph, refs, commit details, and diffs — nothing to configure, nothing to log into.

Built with GPUI for GPU-rendered native UI and gitoxide for reading repositories.

Those links always resolve to the newest tagged release; the filenames never carry a version, which is what keeps them stable. To build from source instead:

cargo install --git https://github.com/HelgeSverre/sourcefour sourcefour

sourcefour            # browse the repository containing the working directory
sourcefour ~/code/foo # browse a specific repository
sourcefour --demo     # browse a generated demo repository

Everything runs through just; just --list shows the recipes, grouped into run, build, check, and dist.

just run      # launch the app on the current repository
just test     # cargo nextest across the workspace
just check    # the full pre-push gate — the same one CI runs
just package  # build dist/Sourcefour.app (ad-hoc signed, local use)

The website lives in website/. Its screenshots — and the one above — are captures of the deterministic demo fixture, regenerated with just screenshots and never edited by hand, so they cannot claim anything the app does not do. --scene names every view worth capturing; the script ships the subset the website and this file use.

CI runs format, lint, tests, and locked debug/release builds on every pull request — Linux only, to keep the bill down, since macOS and Windows minutes bill at 10x and 2x. The full three-platform matrix runs on demand from the Actions tab, and must be run before cutting a release: nothing else checks that the macOS and Windows builds still compile, and the release packages all three.

Releases are cut by cargo-dist. Pushing a version tag runs the test suite first, and only then builds anything:

just release 0.2.0

The .pkg and the .AppImage are maintained alongside the generated jobs because cargo-dist produces neither. release.yml is hand-edited to add the test gate, those two jobs, and the macOS cask publisher, which is why dist-workspace.toml marks ci as allowed-dirty; rerun dist generate after changing dist config and re-apply those edits.

The Homebrew token publishes the formula and cask; the Apple values are what make the .pkg job run. Until they exist, a tag will build everything and then fail at the .pkg step rather than publishing a release with a missing macOS installer.

MIT.