Needs fixing

Needs fixing lists what is broken: pull requests whose latest build failed, pull requests that conflict with their base, and default branches whose checks are failing. Chips at the top narrow the list to CI failing or Merge conflicts. Items are ordered by score; the top five are Do next.

#What you see

CI failing

• CI failing on your PR: the latest build on an open pull request failed. The card names up to three failing checks, for example "CI failing: build, lint and 2 more".
• Trunk CI failing: the default branch is failing in a repository you maintain. It is red if you merged the pull request that landed the failing commit, and amber otherwise.

Merge conflicts

A pull request conflicts with its base, in a repository you can push to. Conflicts in repositories you can only read are left out, so your own work is not buried under other people's stale branches.

#What you can do

• Read the failing check. Go to the item to open the pull request's Overview, where each failing check opens its log. See CI logs.
• Ask the AI. Where the AI features are on, the CI review explains why a check failed. See CI review. AI Fix can fix a failing check. See AI Fix.
• Resolve conflicts opens the conflict resolver, where you decide each conflict yourself. See Resolve merge conflicts.
• A red default branch opens that repository's page with its default branch row open. A failing commit no pull request names opens its checks on GitHub.

#Why it helps

A red build or a conflict stops a pull request from landing until someone acts. This tab puts those items together and names the check that failed, so you can fix it, or ask the person who can.