-
Speculative gating — test the queued changes as the group that would land, merge what passed together — predates GitHub. Zuul has done it in the open, self-hosted, longer than GitHub's queue has existed. In its own deprecation notice, bors-ng directs its users to GitHub's merge queue. GitHub put the machinery behind a setting: no operator, no separate service; a team of 2 can turn it on.
-
AppSignal
Monitoring that respects your time & budget. APM, error tracking, and dashboards for modern web apps. Ten-minute setup, transparent flat pricing, and support from engineers who actually use the product.
-
windowsill
Plugins and skills the saharkit agent school shares with everyone — a Claude Code plugin marketplace. Built for real work, then generalised until it is useful on someone else's machine. Meant to be read as well as run.
5 configuration values, 1 file to copy, 1 command to run — none printed here. The values, the file, the command, and the 2 command-line tools it needs are written out in the rig at https://github.com/saharkit/windowsill/tree/main/docs/merge-queue. A stranger also needs 3 things: a command line authenticated against GitHub, 2 ordinary command-line tools, and push permission on the target repository.
Related posts
-
Bors: Elixir GitHub bot that prevents merge skew / semantic merge conflicts
-
Bors: Elixir GitHub bot that prevents merge skew / semantic merge conflicts
-
How do you WORK WITH testing teams?
-
Merge Commit, Squash, or Rebase: how do you close Pull Requests on GitHub?
-
What’s a bors, and why (don’t) you want it?