Skip to content

Diagnose: PR #67 blocked by status check name mismatch in branch ruleset#72

Merged
Chris-Wolfgang merged 1 commit intodependabot/nuget/dotnet-dependencies-ff70e400d0from
copilot/sub-pr-67-again
Feb 28, 2026
Merged

Diagnose: PR #67 blocked by status check name mismatch in branch ruleset#72
Chris-Wolfgang merged 1 commit intodependabot/nuget/dotnet-dependencies-ff70e400d0from
copilot/sub-pr-67-again

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented Feb 28, 2026

PR #67 (Meziantou.Analyzer 3.0.7 → 3.0.12) is blocked despite all CI passing and having approvals. Root cause identified: the branch ruleset requires a check named Security Scan (CodeQL), but the CodeQL workflow's matrix strategy produces a check named Security Scan (CodeQL) (csharp) — GitHub appends the matrix value to the job name automatically.

Description

Confirmed passing:

  • All 5 jobs in "PR Checks v3 (Gated)" ✅ (Linux/Windows/macOS tests, DevSkim)
  • CodeQL Security Analysis ✅
  • 3 approvals from repo owner ✅
  • Branch up to date, no unresolved review threads ✅

Root cause — check name mismatch:

  • Branch ruleset requires: Security Scan (CodeQL)
  • Actual check run name: Security Scan (CodeQL) (csharp) (matrix job: language: ['csharp'])

Fix needed in branch ruleset settings:
Update the required status check from Security Scan (CodeQL)Security Scan (CodeQL) (csharp) under Settings → Rules. Once updated, PR #67 can merge immediately.

Type of change

  • Bug fix

How Has This Been Tested?

  • Verified all CI check runs via GitHub Actions API — all jobs completed with conclusion: success
  • Confirmed check run name Security Scan (CodeQL) (csharp) via workflow jobs API

Checklist

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes

Screenshots (if applicable)

N/A

Additional context

The Setup-BranchRuleset.ps1 script should also be updated to use Security Scan (CodeQL) (csharp) so newly configured repos don't hit the same mismatch.


💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

Copy link
Copy Markdown
Contributor Author

Copilot AI commented Feb 28, 2026

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

  • https://api.github.com/repos/Chris-Wolfgang/DateTime-Extensions/rulesets
    • Triggering command: /usr/bin/curl curl -s -H Accept: application/vnd.github+json -H X-GitHub-Api-Version: 2022-11-28 -H Authorization: ****** (http block)

If you need me to access, download, or install something from one of these locations, you can either:

Copilot AI changed the title [WIP] Update Meziantou.Analyzer to version 3.0.12 Diagnose: PR #67 blocked by status check name mismatch in branch ruleset Feb 28, 2026
@Chris-Wolfgang Chris-Wolfgang marked this pull request as ready for review February 28, 2026 19:19
Copilot AI review requested due to automatic review settings February 28, 2026 19:19
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot wasn't able to review any files in this pull request.

@Chris-Wolfgang Chris-Wolfgang merged commit 8c76855 into dependabot/nuget/dotnet-dependencies-ff70e400d0 Feb 28, 2026
1 check passed
@Chris-Wolfgang Chris-Wolfgang deleted the copilot/sub-pr-67-again branch February 28, 2026 19:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants