Skip to content

ci: remove per-repo Semgrep scan (the Semgrep Code app covers PRs) - #97

Merged
hyperpolymath merged 1 commit into
mainfrom
chore/drop-duplicate-semgrep
Oct 8, 2026
Merged

hyperpolymath merged 1 commit into
mainfrom
chore/drop-duplicate-semgrep

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

Summary

Removes this repo's own Semgrep scan. The semgrep-code-hyperpolymath GitHub App (Semgrep Managed Scans) already reports semgrep-cloud-platform/scan on every pull request here, so PRs were scanned twice. No ruleset requires a Semgrep context in this repo (checked via rules/branches/main).

No issue. This is owner-requested estate cleanup (duplicate Semgrep scanning).

Type of change

  • 🐛 Bug fix: n/a
  • ✨ New feature: n/a
  • 💥 Breaking change: no. No required check is removed.
  • 🕳️ Soundness fix: n/a
  • 📖 Documentation: n/a
  • 🧹 Refactor / tech debt: n/a
  • ⚡ Performance: n/a
  • 🔧 Build / CI / tooling

📌 New pins

Head SHA: b52809325eccd69ccdfadfcd8e2c42432a64e68e. No pins added or changed.

  • removed: github/codeql-action/upload-sarif@2892aa5e19bbd11bc0cff5427e3b750a04d9e3c2

How has this been verified?

Files:
D .github/workflows/semgrep.yml

No actions.lock in this repo.

  • gh actions-lock --no-fix --json: findings diffed before/after. 0 new findings; only findings that belonged to the removed Semgrep entries disappeared.
  • yq -e . parses every changed YAML file.

Checklist

  • My commits are signed (git commit -S, verified G).
  • I ran the project's own checks/tests locally and they pass: the workflow checks above. The change is CI-only, so no build or test was affected.
  • New files carry the correct SPDX identifier: n/a, no new files.
  • Docs are updated: see notes. Prose that mentions Semgrep is left as is.
  • I have not introduced a soundness hole. The coverage change is flagged below.

Notes for reviewers

Coverage change, stated rather than hidden: the removed workflow also ran on push and schedule. The app reports only on pull requests: no semgrep-cloud-platform/scan check exists on main HEAD 93bfa21. Default-branch and scheduled full scans now depend on Semgrep Cloud's own schedule, which is not verified from GitHub.
After merge the SEMGREP_APP_TOKEN repo secret is unused; the owner approved deleting it then.

🤖 Generated with Claude Code

https://claude.ai/code/session_013aSu89DNALjTYHBvA6FcoM

The semgrep-code-hyperpolymath GitHub App (Semgrep Managed Scans) already
reports semgrep-cloud-platform/scan on every pull request here, so this
workflow scanned the same code twice. No Semgrep context is required by
any ruleset. actions.lock loses only the Semgrep-specific entries.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013aSu89DNALjTYHBvA6FcoM
@coderabbitai

coderabbitai Bot commented Oct 8, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration
  • Configuration used: Organization UI
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: b4c83f88-3d18-4ba0-9df4-46aa497ccfe0
📥 Commits

Reviewing files that changed from the base of the PR and between 93bfa21 and b528093.

📒 Files selected for processing (1)
  • .github/workflows/semgrep.yml
💤 Files with no reviewable changes (1)
  • .github/workflows/semgrep.yml

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

📜 Recent review details
⏰ Context from checks skipped due to timeout. (27)
  • GitHub Check: governance / Debt ratchet
  • GitHub Check: governance / Allowlist Preflight
  • GitHub Check: governance / Security policy checks
  • GitHub Check: governance / Guix packaging policy (Nix retired)
  • GitHub Check: governance / Check Workflow Staleness
  • GitHub Check: governance / Live Actions policy (credentialed advisory)
  • GitHub Check: governance / Exemption ratchet
  • GitHub Check: governance / Licence consistency
  • GitHub Check: governance / Trusted-base reduction policy
  • GitHub Check: governance / Well-Known (RFC 9116 + RSR)
  • GitHub Check: governance / Language / package anti-pattern policy
  • GitHub Check: governance / Workflow security linter
  • GitHub Check: governance / Code quality + docs
  • GitHub Check: scan / gitleaks
  • GitHub Check: scan / shell-secrets
  • GitHub Check: scan / rust-secrets
  • GitHub Check: hypatia / Hypatia Neurosymbolic Analysis
  • GitHub Check: lint-workflows
  • GitHub Check: security
  • GitHub Check: build
  • GitHub Check: Groove manifest check
  • GitHub Check: Validate DEED manifests
  • GitHub Check: Validate K9 contracts
  • GitHub Check: Empty-linter (invisible characters)
  • GitHub Check: analyze (actions, none)
  • GitHub Check: GitGuardian Security Checks
  • GitHub Check: semgrep-cloud-platform/scan

📝 Summary

Summary by CodeRabbit

  • Chores
    • Automated security scans are no longer run when changes are pushed or proposed, on a daily schedule, or on request.
    • Scan results are no longer uploaded as part of this automated process. This changes the repository’s automated security-checking and reporting coverage.

Walkthrough

The Semgrep workflow was deleted. Its triggers, scan job, permissions, and SARIF upload step were removed.

Changes

Security workflow

Layer / File(s) Summary
Remove Semgrep workflow
.github/workflows/semgrep.yml
The workflow that ran Semgrep on pushes, pull requests, a daily schedule, and manual dispatch was removed, along with its scan job and SARIF upload step.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to b5280

The workflow can be removed without an established merge blocker. Confirm Semgrep Cloud’s default-branch and scheduled coverage separately if that coverage is expected.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and concisely describes the removal of the repository-level Semgrep scan to avoid duplicate pull-request scanning.
Description check ✅ Passed The description directly explains the CI change, its rationale, verification steps, and the resulting coverage change.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
  • Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

A rabbit checks the workflow trail,
Then finds the Semgrep steps are stale.
No scan is queued, no SARIF flies,
The config rests beneath the skies.
The rabbit hops away to graze.

Comment @coderabbitai help to get the list of available commands.

@sonarqubecloud

sonarqubecloud Bot commented Oct 8, 2026

Copy link
Copy Markdown

@hyperpolymath
hyperpolymath merged commit c84bc73 into main Oct 8, 2026
35 of 37 checks passed
@hyperpolymath
hyperpolymath deleted the chore/drop-duplicate-semgrep branch October 8, 2026 11:01
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.

1 participant