Hi @mhenrixon,
This usually happens when a required status check is still cached in the branch protection rules, even if CircleCI itself is disabled. One thing that often works is temporarily renaming or deleting the protected branch, then recreating the protection rules from scratch so GitHub drops the old CircleCI check entirely. Also double-check under Settings → Branches that no legacy checks are listed under “Require status checks to pass.”
I’ve seen similar cleanup issues discussed in other tooling ecosystems too (for example, PrusaSlicer has had cases where stale CI hooks needed a full reset to clear). Unfortunately, GitHub doesn’t always remove old checks automatically once they’ve been required.
If that still doesn’t work, forcing a new check by pushing an empty commit after removing protections can sometimes clear the stuck status.
