Join us Oct 28 for a session on AI adoption in engineering with DORA and Honeycomb →
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
· Oct 24, 2025

Use Jira linked issues in initiatives and filters

You can now define how linked work items should be included in your Swarmia initiatives. This makes it easier to track cross-team work, especially if you’re using Jira Plans (previously…
Read more
· Oct 17, 2025

New access control roles: viewer and team admin

You can now use two new roles to control who can edit Swarmia settings in your organization: viewer and team admin . The viewer role is perfect for team members who need visibility into…
Read more