Check the default branches

A broken default branch (often main) affects every open pull request in that repository at once, because each one is tested against it. The strip at the top of Open pull requests shows the default branch of every repository in the workspace, with the result of its latest checks.

#What you see

One row per repository, each with a coloured dot. Point at the dot to read its state:

• CI passing (green): the latest commit’s checks passed.
• CI failing or CI error (red): a check failed on the latest commit. The row names the failing checks.
• CI running (yellow): the checks have not finished.
• No CI reported: GitHub reports no checks for the branch. The dot is a hollow ring.

Each row also says which pull request the latest commit came from, and how long ago. Choose the pull request's number to open it in Limn.

#Open a row

Open a repository's row to see:

• The pull requests that merged into it, up to ten, in merge order. Each row's dot is the result of its newest commit. Hover the commit count to see the commits. A branch that only had direct pushes says so.
• Trunk CI · daily: one cell per day, coloured by how the branch's checks went, with the number of pull requests merged that day above the cells. Hover a cell for its counts. It covers the days Limn keeps history for.
• Flaky marks a check that both passed and failed on the same commit, so a red result may not be the code's fault.

Where else it shows

Each repository page shows the same row for its own branch. A red default branch in a repository you maintain also shows in Needs fixing as Trunk CI failing.

#Why it helps

When main goes red, every open pull request in the repository can look broken. The strip tells you that first, names the pull request that landed the failing commit, and the daily chart shows whether a repository is red now and then or most of the time.