Skip to content

[Tracker] Open PRs that can't merge yet: conflicts and red CI (October 2026) #5654

Open

Description

@CassieFox23

Type: Tracker Status: Active Ecosystem: REA

TL;DR: 304 open pull requests can't merge yet. Each has a conflict, a failing check, or both. Their authors may already be working on them.

Current limitation

Many open pull requests have a merge conflict or a failing check. In a long queue they are easy to miss. This tracker lists them in one place. It is meant to help maintainers and contributors see the whole picture.

Desired outcome and success criteria

Each line below is an open pull request, not a draft, that has a merge conflict, a failing check, or both. Lines are grouped by days since the last activity, then by what blocks the merge. Authors may already be working on these. Nothing here asks for speed, and nothing here is a request to anyone.

A tag after a line says what blocks the merge. (conflicts) means the branch conflicts with main. (CI) means at least one check is failing. (both) means it has both.

0 to 2 days since the last activity (151)

Merge conflict only (68)

Failing CI only (42)

Merge conflict and failing CI (41)

3 to 5 days since the last activity (101)

Merge conflict only (35)

Failing CI only (12)

Merge conflict and failing CI (54)

6 or more days since the last activity (52)

Merge conflict only (9)

Failing CI only (13)

Merge conflict and failing CI (30)

Pull requests where a maintainer asked for changes (5)

A maintainer asked for changes on these 5 at some point. They are also in the groups above. I did not check whether the author has updated them since.

Moved on since opening (315)

Verification details (optional)

I checked each pull request live on 20 October 2026. The fold says how the list is made.

How this list is made
  • Snapshot. I took a snapshot of the open pull requests at about 4:14 PM UTC on 20 October 2026. It held 357 open pull requests that are not drafts and either conflict with main or have a failing check.
  • Live check. I re-read each one live. All 357 were still open. Five had changed. Two now conflict, so they moved to the both group. Three have no conflict now and their checks are running, so they are left out. That leaves 354.
  • Refresh. I refreshed the list at about 7:17 PM UTC on 25 October 2026, using the board as it stood then. 315 moved out, to the Moved on since opening fold. 265 new ones are added. When a pull request's block changes, its line moves to the matching list. Old lines stay in the day group they were in. That makes 304.
  • Last activity. The days count from the author's last push or comment. Maintainer comments do not reset it. A pull request with no author activity counts from its last push.
  • Failing CI. Any failing check counts, whether or not it is required.
  • Changes requested. A review with changes requested, from an owner, member or collaborator who is not the author.
  • Age. Every pull request here is 14 days old or younger.

Related trackers

Every open tracker in the repo, so you can get to any of them from here.

Bugs and duplicates
  • #3537: Open bugs, by subsystem (matbrgz)
  • #4330: Duplicate issues, in clusters (matbrgz)
  • #5653: New issues by area, pointing at #4330 for duplicates (CassieFox23)
Features and roadmap
  • #3796: Feature requests, by area (CassieFox23)
  • #2383: Support for the top 100 languages (matbrgz)
  • #2357: Static file and crash report work (matbrgz)
  • #3714 to #3719: six RFC epics on formats and bytecode (matbrgz)
  • #4027: Browser, Electron and JS work (N0zoM1z0)
  • #32: The main roadmap (morluto)
  • #48: The Evidence v2 epic (morluto)
  • #2039: The roadmap in plain words, a discussion (CassieFox23)
Docs
  • #3795: Open docs issues and PRs (CassieFox23)
Pull requests
  • #3582: Ready to close or merge, issues and PRs (CassieFox23)
  • #5654: Open PRs with conflicts or red CI (this one, CassieFox23)
Show and tell
  • #1435: Linux setup notes and test queue, a discussion (CassieFox23)

🤖 Generated with Claude Code (Sonnet 5.5, verified by Opus 5.5) 🦊

Activity

  1. DeryFerd commented on Oct 22, 2026

    @DeryFerd
    Contributor

    #5262 is not conflict again @CassieFox23 , thanks to @morluto

  2. DeryFerd commented on Oct 22, 2026

    @DeryFerd
    Contributor

    @CassieFox23 #6327 didnt fail any CI Check i think, only some were skipped

  3. CassieFox23 commented on Oct 22, 2026

    @CassieFox23
    ContributorAuthor

    Thanks, DeryFerd, you're right about the current head. On 7ab66ee, 25 checks pass, 19 are skipped, and none fail.

    The (CI) tag means a check was failing when the tracker read the board. That read was at 12:18 PM EDT today. The branch was force-pushed after that, so the tag came from the earlier head. Tonight's tracker refresh moves it to the passing list.

    🤖 Written with Claude Code (Haiku 5.5, verified by Opus 5.5), posted with my OK 🦊

  4. DeryFerd commented on Oct 24, 2026

    @DeryFerd
    Contributor

    @CassieFox23 thank you very much.

    new PRs: #6990 and #6991 are failed because main upstream is still failed, i'll keep updatting it

    update: #6991 is now full green

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions