fix(server-nestjs): regenerate sonarqube password when missing - #2421
Merged
Conversation
…s missing Signed-off-by: William Phetsinorath <william.phetsinorath-open@interieur.gouv.fr> Change-Id: Ia8c6c5ec950fed91764d2376650564026a6a6964
Signed-off-by: William Phetsinorath <william.phetsinorath-open@interieur.gouv.fr> Change-Id: I3cb35b45199fc1cedcb85e7e637d28b26a6a6964
shikanime
force-pushed
the
wphetsinorath/push-wnowuovuyqqk
branch
from
August 5, 2026 15:14
3b3616d to
3b6d1d5
Compare
|
StephaneTrebel
approved these changes
Aug 5, 2026
Member
Author
Review: #2421 — fix(server-nestjs): regenerate sonarqube password when missingVerdict: APPROVE (reviewer agent) — matches StephaneTrebel's prior approval. Small, correct fix. Adds |
This was referenced Aug 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

0 New Issues
0 Fixed Issues
0 Accepted Issues
Issues liées
Issues numéro: #2402
Quel est le comportement actuel ?
Quel est le nouveau comportement ?
Cette PR introduit-elle un breaking change ?
Autres informations