t3837: Skip SonarCloud analysis gracefully when SONAR_TOKEN is missing#3839
t3837: Skip SonarCloud analysis gracefully when SONAR_TOKEN is missing#3839marcusquinn wants to merge 1 commit intomainfrom
Conversation
The SonarCloud scan step ran unconditionally, causing CI failures on all PRs when SONAR_TOKEN was empty. Now the scan is skipped with a warning annotation when the token is not configured, matching the existing Codacy graceful-skip pattern. The summary step also reflects actual SonarCloud status instead of hardcoding 'completed'. Closes #3837
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
🔍 Code Quality Report�[0;35m[MONITOR]�[0m Code Review Monitoring Report �[0;34m[INFO]�[0m Latest Quality Status: �[0;34m[INFO]�[0m Recent monitoring activity: 📈 Current Quality Metrics
Generated on: Sun Mar 8 01:56:10 UTC 2026 Generated by AI DevOps Framework Code Review Monitoring |
|
|
@coderabbitai review Review bots were rate-limited when this PR was created (affected: coderabbitai gemini-code-assist). Requesting a review retry. |
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
|
🧠 Learnings used✅ Actions performedReview triggered.
|
…quinn#3829) Merging: APPROVED (3 reviews), admin author. Failing CI checks (SonarCloud, Monitor & Auto-Fix, Label PR) are systemic issues tracked in marcusquinn#3836/marcusquinn#3837 with fixes in PRs marcusquinn#3838/marcusquinn#3839. Framework Validation, Codacy, and Socket checks all pass.
|
This PR appears orphaned — no active worker process found and no activity for 6+ hours. Flagging for re-dispatch. If work is still in progress, remove the |
|
Merging via pulse supervisor.
|
|
Merge conflict detected — this PR cannot be auto-merged. The branch needs to be rebased onto main. Daily PR cap reached for today; will retry dispatch tomorrow. |
|
Closing — this PR has merge conflicts and touches too many files (blast radius issue, see t1422 / GH#3955). The underlying fixes will be re-created as smaller PRs (max 5 files each) to prevent conflict cascades. Root cause: quality-debt batch PRs touching 10-69 files each created a conflict cascade where each merge invalidated the next PR's base. New rules cap quality-debt PRs at 5 files max and enforce serial merge ordering. |
1 participant
Summary
if: env.SONAR_TOKEN != '') to skip SonarCloud scan when the token secret is not configured, preventing CI failures on all PRs::warning::annotation with setup instructions when skipped, instead of a hard failuresonar-project.propertieshas correctprojectKeyandorganization— no changes neededNote: The
SONAR_TOKENsecret itself must be set manually in GitHub repo settings (Settings > Secrets > Actions). See issue comment for instructions.Closes #3837