Repository navigation
docs : préparer l’annonce Qonto de Gestion 3.4.8 sans release - #681
Merged
Merged
Conversation
baimard
marked this pull request as ready for review
November 10, 2026 07:39
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.
Synchronise le guide développeur avec #680 fusionnée sur master : annonce Qonto à partir de la version choisie 3.4.8, préférences par utilisateur, fermeture avec confirmation serveur, lien de participation et procédure de prochain déclenchement.
Version Sphinx 3.4.8 et site reconstruit. Métadonnées explicitement prepared-not-released, provenance master ac0a0d0 et absence de release_url. L’utilisateur demande la préparation sur master sans publication : aucun tag et aucun workflow de release n’ont été créés.
Validation : Sphinx strict et versioned documentation CI réussis ; source développeur identique à master. Tests applicatifs : 247 tests / 547 assertions, scénarios navigateur et contrôles Nextcloud 32–35 réussis.
Closes #679.