Repository navigation
Add Sonar coverage artifact support - #125
Conversation
TagsThe following tags will be created on main after merge 🏷️ |
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (3)
Included review availability: This review used your included allowance. Your plan provides up to 12 included reviews per hour; 11 remain after this review. 📝 WalkthroughWalkthroughThe reusable SonarQube workflow adds optional inputs to download a coverage artifact before scanning. The README and changelog document the inputs, their use, and the artifact's expected location. ChangesCoverage artifact download
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Feature Sequence Diagram(s)sequenceDiagram
participant TestJob
participant ArtifactStore
participant SonarQubeWorkflow
participant SonarQubeScan
TestJob->>ArtifactStore: Upload coverage artifact
opt coverage-artifact-name is set
SonarQubeWorkflow->>ArtifactStore: Download named artifact to configured path
end
SonarQubeWorkflow->>SonarQubeScan: Run scan
Suggested reviewers: Merge Risk: ⚪ Minimal · up to Coverage remains optional, and the documented dependent job makes its report available before scanning. No actionable merge risk remains. 🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 Generate unit tests (beta)
Comment |
Summary
Testing
npx --yes npm@12.1.0 run ciprettier --check .github/workflows/run_sonar_scan.yml .github/workflows/READMES/run_sonar_scan.md .github/workflows/CHANGELOGS/run_sonar_scan.mdactionlint -ignore 'label "ubuntu-26.04" is unknown' .github/workflows/run_sonar_scan.yml\n-git diff --checkSummary by CodeRabbit