Commit Graph

5 Commits

Author SHA1 Message Date
Christophe Nanteuil 89c55fc592 Simple tool to ease resolving fuzzies (#140)
ci/woodpecker/push/woodpecker Pipeline was successful Details
Display diff of commits introducing fuzzies (commit messages must contain 'merge') using git difftool program, after having filtered the po files [à la mode textconv](https://git.afpy.org/AFPy/python-docs-fr/src/branch/3.11/CONTRIBUTING.rst#configuration-de-git-rendre-plus-lisible-laffichage-des-modifications).

Co-authored-by: Christophe Nanteuil <christophe.nanteuil@gmail.com>
Reviewed-on: #140
Reviewed-by: Julien Palard <julien@palard.fr>
Co-authored-by: Christophe Nanteuil <christophenan@noreply.localhost>
Co-committed-by: Christophe Nanteuil <christophenan@noreply.localhost>
2023-05-23 19:53:36 +00:00
Julien Palard 4b1228c08d
make verifs: Do not wait indefinitely on stdin when nothing changed.
ci/woodpecker/pr/woodpecker Pipeline was successful Details
ci/woodpecker/push/woodpecker Pipeline was successful Details
2023-04-14 14:51:09 +02:00
Julien Palard 3697e62ab7 Colons checker in CI. (#125)
ci/woodpecker/push/woodpecker Pipeline failed Details
Reviewed-on: #125
Reviewed-by: Christophe Nanteuil <christophenan@noreply.localhost>
2023-04-14 11:16:50 +00:00
Julien Palard c584ff6fbb fix colons. (#122)
ci/woodpecker/push/woodpecker Pipeline failed Details
Reviewed-on: #122
Reviewed-by: Christophe Nanteuil <christophenan@noreply.localhost>
2023-04-08 12:37:28 +00:00
Julien Palard c68566b785 Fully working CI (#118)
ci/woodpecker/push/woodpecker Pipeline failed Details
Ça commence à marcher, par contre on a un souci avec un :rfc: dans pospell :

    <rst-doc>:1: (ERROR/3) RFC number must be a number greater than or equal to 1; "la spécification correspondante <5424#section-6>" is invalid. while parsing: La :rfc:`5424` requiert qu’un message Unicode soit envoyé à un démon *syslog* sous la forme d’un ensemble d’octets ayant la structure suivante : un composant ASCII pur facultatif, suivi d’une marque d’ordre d’octet (*BOM* pour *Byte Order Mark* en anglais) UTF-8, suivie de contenu Unicode UTF-8 (voir la :rfc:`la spécification correspondante <5424#section-6>`).

Reviewed-on: #118
2023-04-01 19:44:08 +00:00