Améliore l'affichage de la progression de l 'audit#1115
Merged
bellangerq merged 8 commits intomainfrom May 28, 2025
Hidden character warning
The head ref may contain hidden characters: "868-barre-de-progression-utile-mais-pas-toujours-per\u00e7ue-et-clair-2"
Merged
Conversation
Contributor
|
il faudrait ajouter un point à la fin de chaque phrase :
|
5569cd0 to
1ea6c09
Compare
yaaax
reviewed
May 21, 2025
Collaborator
Contributor
|
@yaaax les boutons doivent ê bleus ./ |
hissalht
approved these changes
May 28, 2025
benoitdequick
approved these changes
May 28, 2025
be9ca93 to
4bd0a91
Compare
Collaborator
Author
|
Ok j'ai reproduit que dans le cas de cette issue : #1126. Ticket dédié du coup ! |
Collaborator
|
Ah. Mais ce n’est peut-être pas possible ? @AdrienMuzyczka Qu’est-ce que t’en dis ? |
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.






closes #868
Il faudra sûrement réajuster le positionnement des éléments en responsive une fois la PR des boutons d'actions mergée (#1110), mais fonctionnellement c'est ok.