GHA: add a job scanning for "bad words" in markdown

This means words, phrases or things we have decided not to use - words that
are spelled right according to the dictionary but we want to avoid. In the
name of consistency and better documentation.

Closes #12764
This commit is contained in:
Daniel Stenberg 2024-01-23 15:12:09 +01:00
parent 2620aa930b
commit e5000e797f
No known key found for this signature in database
GPG key ID: 5CC908FDB71E12C2
93 changed files with 530 additions and 348 deletions

View file

@ -35,7 +35,7 @@ The eleven fields for each CVE in `vuln.pm` are, in order:
### `Makefile`
The new CVE web page file name needs to be added in the `Makefile`'s `CVELIST`
The new CVE webpage filename needs to be added in the `Makefile`'s `CVELIST`
macro.
When the markdown is in place and the `Makefile` and `vuln.pm` are updated,