Skip to content

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

Open

Description

@CassieFox23

Type: Tracker Status: Active Ecosystem: REA

What's here

This list holds 448 open pull requests that can't merge yet. Each has a merge conflict, a failing check, or both. In a long queue they are easy to miss, so this list gathers them in one place. It is meant to help maintainers and contributors see the whole picture. The list is built from what is open on GitHub.

Last refreshed: 2:59 AM UTC on 9 November 2026.

Pull requests that can't merge yet

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 (138)

Merge conflict only (40)

Failing CI only (77)

Merge conflict and failing CI (21)

3 to 5 days since the last activity (40)

Merge conflict only (26)

Failing CI only (6)

Merge conflict and failing CI (8)

6 or more days since the last activity (270)

Merge conflict only (120)

Failing CI only (45)

Merge conflict and failing CI (105)

Pull requests where a maintainer asked for changes (8)

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

The pull requests that left this list are in Moved on since opening, a comment below.

How it's built
  • Start. The list opened on 20 October 2026 with 354 pull requests. Each was open, not a draft, and blocked by a conflict or a failing check.
  • Since then. 735 more were added and 641 moved out, so 448 are listed now. Moved on since opening lists the ones still open.
  • Each refresh. When a pull request's block changes, its line moves to the matching list. Every line is sorted into its day group again.
  • 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. A check is failing when its newest run failed, whether or not it is required. A cancelled or skipped run does not count.
  • Checks passing. Main's four required checks all ran and passed. When those runs wait for a maintainer to approve them, the line says so.
  • Changes requested. A review with changes requested, from an owner, member or collaborator who is not the author.
  • Age. Every pull request here was opened in the last 29 days.

If something's wrong

I refresh this list every so often, so a rebase or a fix shows up on its own. You don't need to post an update. If a line still looks wrong after a refresh, comment on this issue and name the line. I will fix the list.

Related trackers

The main trackers in the repo, so you can get to each one from here.

Bugs and duplicates
Features and roadmap
Docs
Pull requests
Show and tell

Edit (9 Nov): the day groups now follow the author's latest activity. Only a check's newest run counts now, and a cancelled run never counts as failing. In Moved on, "checks passing" now means main's four required checks all passed. Closed and merged ones are counted there, not listed. Moved on now sits in a comment below, so every link here works.

🤖 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

    The tracker above lists open pull requests that can't merge yet. This comment holds the ones that left that list. They sit here because GitHub links only the first 500 issue numbers in one post.

    Moved on since opening (90 listed, 551 closed or merged)

    These were on the list but aren't stuck any more.

    The 551 that closed or merged are left out to keep this list short. This issue's edit history still has them.

    🤖 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

  5. akshad-exe commented on Oct 26, 2026

    @akshad-exe
    Contributor

    @CassieFox23 For the #7054 (conflicts) line: I rebased and pushed the branch; GitHub now reports head 8ab20ab8f as mergeable, and Greptile Review passes on this head. Locally, build:cached, check:fast, docs:check, and the affected focused MCP tests passed. I have not verified a passing full CI run on this head: the current CI run reports action_required with no jobs. Could a maintainer approve/allow that run when convenient? I will address any failures it reports. The tracker line reflects its 25 October snapshot; please update it on the next refresh. Thanks!

  6. moah0911 commented on Oct 29, 2026

    @moah0911

    @CassieFox23 , resolved the merge conflict #7778 , it's good to go

  7. GamerDubz commented on Oct 30, 2026

    @GamerDubz
    Contributor

    @CassieFox23 update for the #3003 (both) line: the conflicts are resolved at bf65bc9e2, and GitHub now reports the PR as mergeable. CI required passed, Greptile passed, and there are no failing or pending checks on this head. Please update that entry on the next refresh. Thanks!

    #7619 still has merge conflicts, so that entry should stay.

  8. GamerDubz commented on Oct 30, 2026

    @GamerDubz
    Contributor

    @CassieFox23 update for the #7619 (conflicts) line: resolved in 239217ca2, and GitHub now reports the PR as mergeable.

    The merge keeps upstream's installation-bound direct registrations and moves the still-needed plugin command runner out of the deleted prewarm module. Locally, 203 setup/service/CLI tests passed (2 Windows skips); typecheck, lint, formatting, docs, architecture and the final build passed. The normal commit and pre-push hooks ran successfully.

    Fresh hosted CI is still running, with no failures reported so far, so I am only reporting the conflict as resolved. Please update that entry on the next refresh. Thanks!

  9. GamerDubz commented on Oct 30, 2026

    @GamerDubz
    Contributor

    @CassieFox23 quick update on #7619 at 1024eead1: the merge conflicts are resolved, and GitHub reports it as mergeable. Greptile passed with no new findings, and all eight test shards plus Portable tests passed.

    CI is still blocked by the macOS arm64 package job. The package repack command exited successfully, but cleanup could not verify a live process's ownership token (malformed_procargs); CI required then failed because of that job. The cause is not confirmed, so I haven't weakened the ownership checks or marked this as fixed.

    I tried rerunning the failed jobs, but GitHub returned Must have admin rights to Repository. Could a maintainer rerun the failed jobs on run 41059655323? For the tracker, this is now CI-only rather than a merge conflict. Thanks!

  10. ArifAli8866 commented on Oct 31, 2026

    @ArifAli8866

    @CassieFox23 update for the #4897 fix(update): bound update subprocess output collection (#4888) (conflicts) line: the merge conflicts are resolved at bd49463a2 (with the PR diff restored strictly to the 3 owning update files), and GitHub now reports the PR as mergeable.

    PR readiness, Validate author declaration, and Greptile Review (5/5, no open findings) have all passed on bd49463a2. Locally, all 148/148 tests across the 7 focused update/process-output test files, check:fast, verify:test-discovery, verify:module-boundaries, format:check, metadata:check, verify:architecture-guards, knip:production, and lint:typed passed. Hosted GitHub Actions workflows on bd49463a2 are currently in action_required awaiting maintainer workflow approval. Please update that entry on the next refresh. Thanks!

  11. changed the title [-][Tracker] Open PRs that can't merge yet: conflicts and red CI (October 2026)[/-] [+][Tracker] Open PRs that can't merge yet: conflicts and red CI[/+] on Nov 5, 2026
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

    area:buildroadmapMulti-issue implementation roadmap

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions