Product

Product Features SDLC How to Compare Docs Screenshots

Start here

Getting started Download Questions

More

Security Roadmap About

Fitting in

What each account scans

An account holding a handful of release repositories and an account that has collected thousands of abandoned feature branches want different answers, and the only place that difference is known is the connection.

Branches per account

A connection carries its own branch list, one name or pattern per line, so release/* works. Empty, or a single star, means every branch and leaves the global setting in charge, which is what every existing connection gets.

What you ask for beats what the estate skips

A skip pattern written for the whole estate that happens to swallow a branch somebody explicitly named is dropped for that scan. The alternative is a scan that reports success and looks at no code at all, which is the one failure on this page nobody notices.

Offered, not typed from memory

A branch box with no idea what exists is a memory test, and a name typed with the wrong case matches nothing and says nothing about it. Every scan records the branches it actually walked, so the box offers the names past scans of that account found with the number of repositories each appears in. The two or three that are really the estate's branches stand out from one person's feature branch, and a click puts one in the box.

Per account, on purpose

Two organizations in different accounts routinely share a repository name. Offering one account's branches while editing another is how somebody ends up scanning nothing at all.

Narrowing is recorded

Narrowing the branches narrows what a scan can possibly find, so the scope goes into the audit record when a connection is saved and onto the connection row, where a thin report can be traced back to it.

What it does not do

The two limits meant for large estates, the cap per repository and the stale branch cutoff, stay global. They are about how long a scan takes rather than about which code somebody wants examined.

Every feature page carries one of those. The comparison page scores the same ground against five products people pay for, including the rows that go against us.

Install it All 30 features