WIP forge-agnostic software release tracker https://earl.run/willow
Go to file
Amolith 804fe9a247
Remove trailing periods to avoid mangled commands
2024-03-05 14:58:57 -05:00
.files add missing screenshots 2024-02-29 15:52:49 -05:00
.reuse initial sourcehut commit 2023-09-21 14:03:21 -04:00
LICENSES remove unused license 2023-12-31 12:17:32 -05:00
cmd Implement new UI, fix DB use 2024-02-23 18:38:44 -05:00
db Actually finish 🤞 DB-/ID-related refactors 2024-02-23 21:16:50 -05:00
git Improve RemoveRepo implementation 2024-02-29 15:51:42 -05:00
project Improve logic around untracking projects 2024-02-29 15:07:07 -05:00
rss finish implementing authentication 2023-10-25 20:16:36 -04:00
users finish implementing authentication 2023-10-25 20:16:36 -04:00
ws Remove 'future' from v sel page 2024-03-05 14:43:33 -05:00
.air.toml ignore future website directory 2023-12-20 14:17:00 -05:00
.gitignore Ignore all SQLite files 2024-02-23 21:24:23 -05:00
.golangci.toml add justfile and ci-lint config 2023-09-24 17:07:42 -04:00
README.md Remove trailing periods to avoid mangled commands 2024-03-05 14:58:57 -05:00
go.mod Bump git-go and its deps 2024-02-23 18:52:05 -05:00
go.sum Bump git-go and its deps 2024-02-23 18:52:05 -05:00
go.sum.license reuse compliance 2023-09-24 16:57:56 -04:00
justfile Beeg refactor for database and users and auth 2023-10-25 00:14:32 -04:00



Go report card status REUSE status Donate with fosspay

Forge-agnostic software release tracker

screenshot of willow's current web UI

This UI is Amolith's attempt at a balance between simple, pleasant, and functional. Amolith is not a UX professional and would very much welcome input from someone more knowledgeable!

What is it?

If you'd rather watch a short video, Amolith gave a 5-minute lightning talk on Willow at the 2023 Ubuntu Summit.

Willow helps developers, sysadmins, and homelabbers keep up with software releases across arbitrary forge platforms, including full-featured forges like GitHub, GitLab, or Forgejo as well as more minimal options like cgit or stagit.

It exists because decentralisation, as wonderful as it is, does have some pain points. One piece of software is on GitHub, another piece is on GitLab, one on Bitbucket, a fourth on SourceHut, a fifth on the developer's self-hosted Forgejo instance.

The capabilities of each platform can also differ, further complicating the space. For example, Forgejo and GitHub have APIs and RSS release feeds, SourceHut has an API and RSS feeds that notify you of all activity in the repo, GitLab only has an API, and there's no standard for discovering the capabilities of arbitrary git frontends like legit.

And then you have different pieces of information in different places; some developers might publish release announcements on their personal blog and some projects might release security advisories on an external platform prior to publishing a release.

All this important info is scattered all over the internet. Willow brings some order to that chaos by supporting both RSS and one of the very few things all the forges and frontends have in common: their Version Control System. At the moment, Git is the only supported VCS, but we're definitely interested in adding support for Pijul, Fossil, Mercurial, and potentially others.

Amolith (the creator) has recorded some of his other ideas, thoughts, and plans in his wiki.

Installation and use


  1. Prebuilt binaries will be available with the v0.0.1 release, greatly simplifying installation.
  2. We consider the project alpha-quality. There will be bugs.
  3. Amolith has tried to make the web UI accessible, but is unsure of its current usability.
  4. The app is not localised yet and English is the only available language.
  5. Help with any/all of the above is most welcome!


This assumes Willow will run on an always-on server, like a VPS.

  • Clone the repo with git clone https://git.sr.ht/~amolith/willow
  • Enter the repo's folder with cd willow
  • Build the binary with CGO_ENABLED=0 go build -ldflags="-s -w" -o willow ./cmd
  • Transfer the binary to the server however you like
  • Execute the binary with ./willow
  • Edit the config with vim config.toml
  • Daemonise Willow using systemd or OpenRC or whatever you prefer
  • Reverse-proxy the web UI (defaults to localhost:1313) with Caddy or NGINX or whatever you prefer


  • Create a user with ./willow -a <username>
  • Open the web UI (defaults to localhost:1313, but installation had you put a proxy in front)
  • Click Track new project
  • Fill out the form and press Next
  • Indicate which version you're currently on and press Track releases
  • You're now tracking that project's releases!

If you no longer use that project, click the Delete? link to remove it, and, if applicable, Willow's copy of its repo.

If you're no longer running the version Willow says you've selected, click the Modify? link to select a different version.

If there are projects where your selected version does not match what Willow thinks is latest, they'll show up at the top under the Outdated projects heading and have a link at the bottom of the card to View release notes. Clicking that link populates the right column with those release notes.

If there are projects where your selected version does match what Willow thinks is latest, they'll show up at the bottom under the Up-to-date projects heading.


Contributions are very much welcome! Please take a look at the ticket tracker and see if there's anything you're interested in working on. If there's specific functionality you'd like to see implemented and it's not mentioned in the ticket tracker, please describe it through one of the platforms below so we can discuss its inclusion. If we don't feel like it fits with Willow's goals, you're encouraged to fork the project and make whatever changes you like!

Questions, comments, and patches can always go to the mailing list, but there's also an IRC channel and an XMPP MUC for real-time interactions.

If you haven't used mailing lists before, please take a look at SourceHut's documentation, especially the etiquette section.

Configuring git...

…for git send-email

git config sendemail.to "~amolith/willow@lists.sr.ht"
git config format.subjectPrefix "PATCH willow"
git send-email [HASH]

…for signing the DCO

git config format.signOff yes

Required tools

  • Go
  • gofumpt
    • Stricter formatting rules than the default go fmt
  • golangci-lint
    • Aggregates various preinstalled Go linters, runs them in parallel, and makes heavy use of the Go build cache
  • Staticcheck
    • Uses static analysis to find bugs and performance issues, offer simplifications, and enforce style rules

Suggested tools

  • just
    • Command runner to simplify use of the required tools
  • air
    • Watches source files and rebuilds/executes the project when sources change