You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
MPT-27624 Restore the original SonarCloud project key - #155
Set sonar.projectKey in backend/sonar-project.properties back to softwareone-platform_swo-extension-playground.
Why
The repo rename (#107) changed the key to softwareone-platform_mpt-extension-python-template, but the SonarCloud project was only renamed and kept its original key. Since then the scan has reported to a new, auto-created project with default settings:
PRs had no main-branch baseline, so "new code" in the quality gate was measured against nothing.
Results stopped being exported to GitHub code scanning, so PRs lost the SonarCloud check that the other mpt-* repos show.
With the original key, analyses go back to the existing project and its history.
Follow-up
After merge, a SonarCloud organization admin should delete the auto-created project softwareone-platform_mpt-extension-python-template.
Testing
make check scope=backend and make test scope=backend pass locally (40 tests).
This PR's own checks should show SonarCloud Code Analysis linking to softwareone-platform_swo-extension-playground.
Reviewing files that changed from the base of the PR and between 242ab39 and beacfd5.
You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.
Use the checkbox below for a quick retry:
Trigger review
No actionable comments were generated in the recent review.
Walkthrough
The SonarQube project key changes from softwareone-platform_mpt-extension-python-template to softwareone-platform_swo-extension-playground. Other project settings remain unchanged.
The SonarQube project key is restored as intended and is ready to merge.
Pre-merge checks: 2 · 1
Failed checks: 1 warning
Check name
Status
Explanation
Resolution
Documentation Up To Date
The PR changes the SonarCloud integration destination in backend/sonar-project.properties:1. The CI workflow runs the Sonar scan with projectBaseDir: backend in `.github/workflows/pr-build-merge.y…
Add or update repository documentation in the same PR. Document the SonarCloud organization, project key, and CI integration destination in docs/external-integrations.md (or the repository’s designated integration document), and link it f…
Passed checks: 2 passed
Check name
Status
Explanation
Linked Issues check
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
Check skipped because no linked issues were found for this pull request.
Full details: Documentation Up To Date
Explanation
The PR changes the SonarCloud integration destination in backend/sonar-project.properties:1. The CI workflow runs the Sonar scan with projectBaseDir: backend in .github/workflows/pr-build-merge.yml:67-73, so this change affects the external quality-gate integration. Existing docs/testing.md:45 documents the SonarCloud scan but does not document the project key or destination, and no documentation file changed in this PR. The shared documentation standard requires documentation for relevant external integrations (repository softwareone-platform/mpt-extension-skills, commit 9d8bcd7148e89c32545cf1ad5f80370036713e25, standards/documentation.md:30-31,77).
Resolution
Add or update repository documentation in the same PR. Document the SonarCloud organization, project key, and CI integration destination in docs/external-integrations.md (or the repository’s designated integration document), and link it from the documentation map if needed. Update docs/testing.md only if the SonarCloud quality-gate behavior requires additional workflow details.
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Included review availability: This review used your included allowance. 1 included review remains after this review. Your included PR review attempts over the past 7 days set your current allowance at 5 reviews per hour.
Recent review details
Context from checks skipped due to timeout: 2
GitHub Check: CodeRabbit
GitHub Check: build
Additional context used
Path-based instructions: 2
Review backend changes against `AGENTS.md`, `docs/architecture.md`, `docs/contributing.md`, and `docs/testing.md`.
CodeRabbit configuration file
Files:
backend/sonar-project.properties
For each subsequent commit in this PR, explicitly verify if previous review comments have been resolved
The repo rename changed sonar.projectKey to
softwareone-platform_mpt-extension-python-template, but the SonarCloud
project was only renamed and kept its original key. Analyses went to a
new, empty project with default settings: PRs had no main-branch
baseline and stopped exporting results to GitHub code scanning.
Point the scan back at softwareone-platform_swo-extension-playground so
it reports to the original project and its history again.
svazquezco
deleted the
bugfix/MPT-27624/update-sonarcloud-project-key-mpt-extension-python-template
branch
November 4, 2026 13:14
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
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.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
🤖 AI-generated PR — Please review carefully.
What
Set
sonar.projectKeyinbackend/sonar-project.propertiesback tosoftwareone-platform_swo-extension-playground.Why
The repo rename (#107) changed the key to
softwareone-platform_mpt-extension-python-template, but the SonarCloud project was only renamed and kept its original key. Since then the scan has reported to a new, auto-created project with default settings:SonarCloudcheck that the othermpt-*repos show.With the original key, analyses go back to the existing project and its history.
Follow-up
After merge, a SonarCloud organization admin should delete the auto-created project
softwareone-platform_mpt-extension-python-template.Testing
make check scope=backendandmake test scope=backendpass locally (40 tests).SonarCloud Code Analysislinking tosoftwareone-platform_swo-extension-playground.Closes MPT-27624
sonar.projectKeytosoftwareone-platform_swo-extension-playgroundso SonarCloud analyses use the existing project.