Transitioning the team from nothing to Clean Code culture (with code coverage)

SonarQube Cloud
1

Template for a good new topic, formatted with Markdown:

  • ALM used (GitHub)
  • CI system used (github Action)
  • Languages of the repository : Java + SpringBoot

We are just starting with SC, and while it’s ok to have red state CI for each PR, we would like to avoid having a red state on the main branch (we want to be able to improve step by step).

Is it possible on main to upload the new analysis (when we merge a PR) but not generate a red state (meaning not blocking the CI) if it doesn’t match the Quality gate ?

2

Hey there.

Blocking the CI shouldn’t be something that is happening by default. How is your GitHub Action configured? Feel free to share the YAML here.