Skip to content

CI has failed on every merge to main, but PRs keep merging — main needs a required status check #500

Open

Description

@chonilius

Problem

gh run list -b main shows the last five pushes to main (merges of #454, #456, #453, #467 and #469 on 2026-09-27/28) all ended in failure. main now doesn't type-check, and 17 of 47 Jest suites fail even after patching the three syntax errors. Breakage accumulated because nothing stops a PR merging while the pipeline is red.

Suggested fix

Turn on branch protection for main that requires the CI Pipeline job and requires branches to be up to date before merging. Most of the merge damage here comes from PRs that were green against an older main.

Related: #156

Activity

  1. added
    bugSomething isn't working
    testingTesting/QA infrastructure
    Stellar WaveIssues in the Stellar wave program
    on Oct 13, 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

    Stellar WaveIssues in the Stellar wave programbugSomething isn't workingtestingTesting/QA infrastructure

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions