Why a red main branch is expensive
A failing build on the default branch stops the whole team. New work cannot be trusted, because nobody knows whether a failure is theirs. Deploys stop. The person who broke it may have gone home.
It is also usually a small fix: a renamed function, a test that assumed yesterday’s behaviour, a type that changed.
What starts the work
Bugstack does autonomous software maintenance, and it hears about CI from GitHub. Two things start a fix:
- A failed run on your default branch. A real failure, a timeout, or a run that could not start.
- The same check failing on several branches at once. If one check fails on three or more branches within a day while main is still green, something shared has broken.
There is nothing to install in your CI. It works with GitHub Actions and with any CI that reports its results to GitHub, such as CircleCI, Jenkins or Buildkite.
What Bugstack does with it
- Reads the failed run and the commits since the last green one.
- Decides what is wrong. There are three possible answers: the code is wrong, the test is wrong, or there is nothing to fix in the repository.
- Opens a pull request with the change, and says which of the three it found and why.
- Stands down if the branch goes green on its own in the meantime.
Your CI runs on the pull request like any other. On Review you merge it.
What it leaves alone
- Your CI configuration. Bugstack never writes to workflow files or other CI config. If the config is what broke, it tells you.
- Flaky checks. A check that fails and then passes on the same commit is reported as flaky. Bugstack does not paper over it with a fix.
- Its own failed attempts. If a Bugstack pull request fails your CI, it makes one more attempt on the same branch and then stops and tells you.
Who this is for
- A small team where a red build at six in the evening stays red until morning.
- A solo builder whose deploys depend on a green branch.
- Anyone who has opened their laptop to find main broken by a change they did not make.
How to start
- Sign in with GitHub and start the 14-day trial. It includes $50 of credit.
- Install the Bugstack GitHub App on your repository.
That is all this job needs. No SDK is required for CI fixes.
Questions
Does it work with my CI provider?
If your CI reports check results or commit statuses on GitHub, yes. That covers GitHub Actions, CircleCI, Jenkins, Buildkite and most others.
Will Bugstack push to my main branch?
It opens a pull request. On Review, where every repository starts, you merge it. On Autopilot it merges once your proof setting is met.
What if the test was right and the code was wrong?
That is one of the three answers it can reach, and it fixes the code. If the test was asserting old behaviour, it fixes the test and says so in the pull request, so you can disagree.