Skip to content

chore: explain why code/snyk GitHub App check persists despite workflow disable#559

Merged
MightyPrytanis merged 2 commits intodependabot/npm_and_yarn/apps/lexfiat/vite-8.0.1from
copilot/sub-pr-541-again
Mar 21, 2026
Merged

chore: explain why code/snyk GitHub App check persists despite workflow disable#559
MightyPrytanis merged 2 commits intodependabot/npm_and_yarn/apps/lexfiat/vite-8.0.1from
copilot/sub-pr-541-again

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented Mar 21, 2026

The code/snyk (mightyprytanis) check continues to appear on PRs even though snyk-security.yml is disabled. This is because Snyk (and Semgrep) each have a GitHub App integration that triggers PR checks independently of any workflow file — disabling the workflow has no effect on the App.

Status of each check

Check Source Status
snyk-security.yml GitHub Actions workflow ✅ Disabled (workflow_dispatch only + if: ${{ false }})
codeql.yml GitHub Actions workflow ✅ PR trigger removed
semgrep.yml GitHub Actions workflow ✅ PR trigger removed
SnykCode / code/snyk (mightyprytanis) Snyk GitHub App ⚠️ Still running — must be disabled externally
semgrep-cloud-platform/scan Semgrep GitHub App ⚠️ Still running — must be disabled externally

Required action (cannot be done via code)

To stop code/snyk from running on PRs, one of:

  • Snyk dashboard → Settings → GitHub integration → disable PR checks or disconnect the repo
  • GitHub → Settings → GitHub Apps → Snyk → Configure → remove this repository from its access list

Same applies to semgrep-cloud-platform/scan if that check also needs to stop blocking auto-merges.


💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Copilot AI changed the title [WIP] Build(deps): bump vite from 7.3.1 to 8.0.1 chore: explain why code/snyk GitHub App check persists despite workflow disable Mar 21, 2026
Copilot AI requested a review from MightyPrytanis March 21, 2026 12:06
@MightyPrytanis MightyPrytanis marked this pull request as ready for review March 21, 2026 13:15
Copilot AI review requested due to automatic review settings March 21, 2026 13:15
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.

@MightyPrytanis
Copy link
Copy Markdown
Owner

@copilot I have manually disabled Snyk code, yet it is still showing up. Why?

Copy link
Copy Markdown
Contributor Author

Copilot AI commented Mar 21, 2026

@copilot I have manually disabled Snyk code, yet it is still showing up. Why?

Two things to clarify here:

1. SnykCode is NOT blocking this PR — it's showing as ✅ success (and completes in ~1 second, so it's effectively a no-op). Disabling "Snyk Code" in Snyk's dashboard turns off the scan itself but the GitHub App still posts a pass-through check run. To make it disappear entirely, you'd need to uninstall/revoke the Snyk GitHub App from this repo in GitHub Settings → Apps.

2. The actual blocker is Quality Gates — it's failing because Cyrano's test suite ran at 81.16% pass rate (56/69 tests passing, 13 failing), which is below the 85% threshold in ci.yml. This is a pre-existing Cyrano test failure unrelated to the Vite bump in this PR.

The auto-approve/auto-merge steps also showed as skipped because Vite 7→8 is a major version update, which the Dependabot auto-merge workflow intentionally excludes (it only auto-merges patch and minor updates).

@MightyPrytanis MightyPrytanis merged commit 37b3fbe into dependabot/npm_and_yarn/apps/lexfiat/vite-8.0.1 Mar 21, 2026
4 of 5 checks passed
@MightyPrytanis MightyPrytanis deleted the copilot/sub-pr-541-again branch March 21, 2026 14:59
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