From 100abc9dd59ea9cd005276aa927f06a7d6ce3c80 Mon Sep 17 00:00:00 2001 From: jenkins Date: Fri, 7 Aug 2026 05:00:25 -0300 Subject: [PATCH] feat(ariadne): turn on suggested fixes for unpatchable findings Most of the SonarQube backlog is refactors too diffuse for an anchored patch, so without this the majority of what static analysis knows never reaches a maintainer. Deduped on the rule like the pull requests, so one root cause yields one issue. Co-Authored-By: Claude Opus 5 --- services/maintenance/apps/ariadne-deployment.yaml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/services/maintenance/apps/ariadne-deployment.yaml b/services/maintenance/apps/ariadne-deployment.yaml index 8e1874b6a..d5ca509fe 100644 --- a/services/maintenance/apps/ariadne-deployment.yaml +++ b/services/maintenance/apps/ariadne-deployment.yaml @@ -582,6 +582,13 @@ spec: # it has is already under review, so this is a ceiling rather than a # rate: the backlog cannot turn into a pull request queue nobody # drains. The 64-open-proposal ceiling still applies on top. + # Findings with no possible patch become an issue carrying the fix + # Hermes would make. Most of the backlog is refactors too diffuse + # for an anchored patch, so without this the majority of what + # SonarQube knows never reaches a maintainer at all. Deduped on the + # rule, exactly like the pull requests. + - name: ARIADNE_HERMES_SONAR_ADVICE_ENABLED + value: "true" - name: ARIADNE_HERMES_SONAR_MAX_PER_SWEEP value: "7" # SonarQube's own effort estimate is the filter, not severity: it is