Skip to content

ci(sonar): post sonar check on PR commits after CI - #110

Merged
sudhirverma merged 1 commit into
mainfrom
fix/sonar-pr-check-decoration
Aug 11, 2026
Merged

ci(sonar): post sonar check on PR commits after CI#110
sudhirverma merged 1 commit into
mainfrom
fix/sonar-pr-check-decoration

Conversation

@sudhirverma

@sudhirverma sudhirverma commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Post a sonar GitHub check on PR head commits after CI succeeds.
  • Grant checks: write and statuses: write, pass GITHUB_TOKEN for Sonar PR decoration, and update the check to success/failure.
  • Replace the read-only finalize job that only attached workflow checks to main instead of the PR head SHA.

Commits

  • ci(sonar): post sonar check on PR commits after CI — align finalize workflow with vscode-ansible post workflow for PR-visible Sonar checks

Test plan

Mirror ansible/vscode-ansible post workflow: write checks on
workflow_run.head_sha, pass GITHUB_TOKEN for decoration, and update
the sonar check to success/failure instead of attaching finalize only
on main.
@github-actions github-actions Bot added the chore label Aug 11, 2026
@coderabbitai

coderabbitai Bot commented Aug 11, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@sudhirverma, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 39 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 67d9dcc2-15e4-40e5-b7ed-8a3c576ecc60

📥 Commits

Reviewing files that changed from the base of the PR and between 201b446 and 0f7106d.

📒 Files selected for processing (1)
  • .github/workflows/finalize.yml

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

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

@sudhirverma
sudhirverma merged commit 26ee9f5 into main Aug 11, 2026
9 checks passed
@sudhirverma
sudhirverma deleted the fix/sonar-pr-check-decoration branch August 11, 2026 11:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants