[chore] migrate Sonar analysis to self-hosted SonarQube - #3
Merged
Merged
Conversation
SonarCloud was retired org-wide (pathorsAI/pathors#2250); analysis now runs CI-based against https://sonar.pathors.com, same as the pathors monorepo. Adds the single-project sonar.yml workflow and sonar-project.properties.
After every scan the workflow now posts (or updates in place) one PR comment with the Quality Gate verdict, any failed conditions, the open issues on the PR, and a link to the dashboard — so nobody has to open the Sonar UI to learn how the gate went. Best-effort: a comment that could not be posted never turns a green scan red.
✅ SonarQube Quality Gate passed — pathorsAI_n8n-node-pathors0 open issues on this PR. |
YJack0000
enabled auto-merge (squash)
August 23, 2026 17:53
yui0303
approved these changes
Aug 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Moves Sonar analysis off SonarCloud and onto the self-hosted SonarQube instance (
sonar.pathors.com), following the org-wide retirement of SonarCloud in pathorsAI/pathors#2250..github/workflows/sonar.yml— CI-based scan, single project (no matrix, unlike the monorepo's version). Runs on pushes tomain, same-repo PRs, andworkflow_dispatch. Fork PRs are skipped (they cannot readSONAR_TOKEN). PR analysis works via the community-branch-plugin with the samesonar.pullrequest.*properties SonarCloud used.sonar-project.properties— project key, exclusions,sonar.qualitygate.wait=true, and the same coverage-parity call as the monorepo (sonar.coverage.exclusions=**until an lcov import exists).Notes
SONAR_TOKENrepo secret is already in place (a dedicated global analysis token for public repos, tracked in patchbay assonarqube-ci-analysis-token-public-repos).mainafter merge seeds the branch baseline; this PR's own run exercises the PR-analysis path.