Skip to content

CTA SonarCloud Hackaton

Summary

Organise 2 days of collective development work to fix SonarCloud issues on the CTA project:

Planning

To be prepared by @afonso :

  • Split issues by category (security/reliability/maintainability/etc), severity (blocking/high/etc) and rule.
    • Order priority and number of occurrences.
  • Each developer will pick a separate set of rules, one-by-one, and fix them.
  • How can we streamline merge requests to main?
    • Enable MR chaining in gitlab ? (Yes/No)
    • Allowing self-approval ? (Yes/No)
    • Allowing multiple rule fixes to go in the same MR ? (Yes/No)
    • Other ?
Edited by Joao Afonso