chore(ci): remove duplicate self-run SonarQube workflow - #69
Conversation
cicd-squabbler runs Sonar analysis twice. The SonarCloud App (app=sonarqubecloud) emits the required `SonarCloud Code Analysis` context and is green. This workflow additionally runs SonarSource/sonarqube-scan-action itself, emitting a separate `SonarQube` check (app=github-actions) that is red on every push. Measured on main HEAD be78284: failure SonarQube app=github-actions <- this file success SonarCloud Code Analysis app=sonarqubecloud <- the App The two are different apps, so removing this workflow cannot take the required App check with it. `SonarQube` is not a required context on ruleset 18261844 (required: CodeQL, openssf-compliance, SonarCloud Code Analysis), so nothing turns absent. `sonarqube.yml` is listed under `never_required_workflows` in standards/config/rulesets/gates.json, so deletion is consistent with estate policy. sonar-project.properties is retained -- automatic analysis still reads its scope and exclusions. The repo has no actions.lock, so there is no pin entry to keep in sync. Net effect: one less wasted runner per push, and one less permanently red check on the board. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TCKh98NmUmfvgpuGyJbNu8
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (1)
💤 Files with no reviewable changes (1)
Included review availability: 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. (4)
|
| Layer / File(s) | Summary |
|---|---|
Remove SonarQube workflow .github/workflows/sonarqube.yml |
Deletes the SonarQube workflow and its scan configuration. |
Priority: ⬇️ Low
Estimated code review effort: 1 (Trivial) | ~2 minutes
Merge Risk: ⚪ Minimal · up to fa84f
This change removes the duplicate SonarQube workflow while retaining the SonarCloud configuration and required SonarCloud App analysis. No current merge-blocking risk is identified.
🚥 Pre-merge checks | ✅ 4 | ❌ 1
❌ Failed checks (1 warning)
| Check name | Status | Explanation | Resolution |
|---|---|---|---|
| Description check | The description gives a clear reason, scope, safety assessment, and provenance for deleting the workflow. However, it does not use the required Summary, Changes, RSR Quality Checklist, Testing, or Scr… | Rewrite the description using the repository template. Add the required headings, list the workflow deletion under Changes, complete the applicable RSR Quality Checklist items, and document testing or state why testing is not applicable. In… |
✅ Passed checks (4 passed)
| Check name | Status | Explanation |
|---|---|---|
| Title check | ✅ Passed | The title clearly and concisely states the main change: removal of the duplicate self-run SonarQube workflow. |
| 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. |
Full details: Description check
Explanation
The description gives a clear reason, scope, safety assessment, and provenance for deleting the workflow. However, it does not use the required Summary, Changes, RSR Quality Checklist, Testing, or Screenshots sections, and it provides no test results or completed checklist items.
Resolution
Rewrite the description using the repository template. Add the required headings, list the workflow deletion under Changes, complete the applicable RSR Quality Checklist items, and document testing or state why testing is not applicable. Include screenshots or terminal output if applicable.
✨ Finishing Touches
🛠️ Fix failing CI checks
- Create stacked PR
- Commit on current branch
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.
A rabbit finds the workflow gone
No sonar scan runs at dawn
The tokens rest
The pipeline is less
And carrots roll on>
Comment @coderabbitai help to get the list of available commands.
|
|
✅ Coding Agent task started: View task and status The task will inspect the CI failures, validate its fix, and open a stacked fix pull request automatically.
|



What
Deletes
.github/workflows/sonarqube.yml. Keepssonar-project.properties.Why
cicd-squabbler analyses with Sonar twice. Measured on
mainHEADbe78284:failureSonarQubegithub-actions— this workflowsuccessSonarCloud Code Analysissonarqubecloud— the AppThe SonarCloud App performs automatic analysis and emits the required
SonarCloud Code Analysiscontext on its own. The self-run workflow addsnothing but a second scan that fails on every push, burning a runner and
leaving a permanently red check on the board.
Why this is safe
app=sonarqubecloud;this workflow emits
app=github-actions. Deleting the file cannot take therequired check with it.
SonarQubeis not required. Ruleset18261844(Optimus-Branch,target=branch,enforcement=active) requires exactly three contexts:CodeQL,openssf-compliance,SonarCloud Code Analysis. No gate turnsabsent.
sonarqube.ymlis listed undernever_required_workflowsinstandards/config/rulesets/gates.json.actions.lock(404 at root,absent from
.github/workflows/), so there is no pin entry left dangling.sonar-project.propertiesstays; automaticanalysis reads its exclusions.
Provenance
Found by the dead-app / wasted-runner sweep (report:
.claude/reports/2026-09-08-dead-app-config-sweep.md, §5 "Wasted runner").Ruleset rollback JSON captured before any inspection.
🤖 Generated with Claude Code
https://claude.ai/code/session_01TCKh98NmUmfvgpuGyJbNu8