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

Remove sonarqube CI workflow #570

Merged
merged 1 commit into from
Jun 25, 2024

Conversation

johannaengland
Copy link
Contributor

Sonarqube already automatically analyses this repo, we don't need this workflow.
See for example: #568 (comment)

More info about automatic analysis: https://docs.sonarsource.com/sonarcloud/advanced-setup/automatic-analysis

Sonarqube already automatically analyses this repo, we don't need this workflow
@johannaengland johannaengland self-assigned this Jun 21, 2024
Copy link

@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Please upload report for BASE (master@b738b81). Learn more about missing BASE report.

Additional details and impacted files
@@            Coverage Diff            @@
##             master     #570   +/-   ##
=========================================
  Coverage          ?   57.34%           
=========================================
  Files             ?       86           
  Lines             ?     3692           
  Branches          ?      840           
=========================================
  Hits              ?     2117           
  Misses            ?     1566           
  Partials          ?        9           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@johannaengland johannaengland merged commit 6895f57 into master Jun 25, 2024
3 of 4 checks passed
@johannaengland johannaengland deleted the workflows/remove-sonarqube-workflow branch June 25, 2024 08:17
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.

3 participants