The mediawiki/extensions/ContentTranslation repository has a yamllint job I would like to phase out T95890. The repository has a composer entry which runs composer test. Can you add a test that validates your yaml files so I can phase out the generic yamllint job? Thanks!
Description
Description
Details
Details
Related Changes in Gerrit:
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Removed deprecated yamlint for ContentTranslation | integration/config | master | +0 -3 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | hashar | T95890 Phase out yamllint jobs | |||
| Declined | Amire80 | T95892 Add a PHP test to lint ContentTranslation yaml files |
Event Timeline
Comment Actions
Change 242446 had a related patch set uploaded (by KartikMistry):
Removed deprecated yamlint for ContentTranslation
Comment Actions
CI configuration is gone. Thanks. You will most probably want to add a composer/npm runnable test to lint the YAML files.
Comment Actions
Change 242446 merged by jenkins-bot:
Removed deprecated yamlint for ContentTranslation
Comment Actions
Turns out there is no YAML file in the repository beside the rubocop configuration file. If it ever become invalid, the rubocop job will fail.
Comment Actions
A yaml test is not really needed in ContentTranslation, because the only yaml file that we have there is the rubocop configuration, and it can test itself, and we don't expect any more yaml files.