Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CI: New branch name pattern for full Sonar analyses #22

Merged
merged 1 commit into from
Sep 13, 2023

Conversation

So-Fras
Copy link
Member

@So-Fras So-Fras commented Sep 13, 2023

Please check if the PR fulfills these requirements

  • The commit message follows our guidelines

What kind of change does this PR introduce?
Feature

What is the current behavior?
Full sonar analyses are only performed on main and release-v** branches.

What is the new behavior (if this is a feature change)?
Full sonar analyses will also be performed for full-sonar-analysis-** branches.

Other information:
This PR is not sufficient. To have full sonar analyses on these branches, the pattern must also be added to the "long-living branches" definition in the SonarCloud project.
(To have a full report, the analysis must be performed on a branch and not a PR - this is the purpose of this PR - AND the branch must be a long-living one.)

See powsybl/powsybl-diagram#541 for more information.

@So-Fras So-Fras requested a review from annetill September 13, 2023 13:05
@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@So-Fras So-Fras merged commit 0f60867 into main Sep 13, 2023
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants