We raised an $11M Series A led by Karma and DIG Ventures →
Changelog · Mar 2, 2021

Track unreviewed code pushed straight to the main branch

Code review helps ensure code quality, and share knowledge within the team. Yet even among teams performing code reviews regularly, pushing unreviewed code to master is not uncommon. Our new working agreement helps track all commits merged to your main branch without review, and start a conversation within the team if it becomes an issue.

See how your team is doing under Explore → We don’t push code directly to main branch. Connect Swarmia’s Slack digest to get a daily summary of all unreviewed code pushed to production.

Select what teams to see in Swarmia

choose teams

Now you can choose GitHub teams to show in Swarmia, and hide teams that do not represent actual development teams in your organisation: for example, if you use teams for access control. We’ve hidden some of these teams automatically based on Swarmia usage. 👉 See them all here.

Other improvements

  • Pull request dots in all scatter plots now link to GitHub
  • Better auto-complete suggestions when searching for projects in Jira configuration settings
  • Switching the team now preserves the selected working agreement

Subscribe to our newsletter
Get the latest product updates and #goodreads delivered to your inbox once a month.

More changelog updates
· Jun 16, 2025

Define hotfixes with pull request and issue filters for more accurate change failure metrics

Change failure rate and mean time to recovery are two of the four key DORA metrics, helping you understand how often your deployments cause problems in production and how quickly you can…
Read more
· Jun 12, 2025

Add context to pull requests and issues with notes

Sometimes numbers only tell a part of the story. A pull request might have taken longer than usual due to unexpected complexity, scope changes, or external blockers. An issue might be an…
Read more