Add Gherkin lint action

[ernilambar]

No description provided.

[swissspidy]

Seems to work 👍 GitHub Actions annotations would be a bonus, but not a requirement.

This would be something for https://github.com/wp-cli/.github

[swissspidy]

GitHub Actions annotations would be a bonus, but not a requirement.

It might be doable with a custom problem matcher https://fusectore.dev/2021/11/19/github-action-problem-matchers.html

[ernilambar]

@swissspidy

Where should the lint-gherkin.yml and .gherkin-lintrc files reside? https://github.com/wp-cli/.github/ ?
Should we implement like reusable-XXX.yml?

[swissspidy]

The Gherkin lint job should be part of the existing reusable-code-quality.yml file in the .github repository.

Do we need a custom .gherkin-lintrc? If so, we could try finding a way to have that in the .github repo as well. Otherwise we would need to copy to file to all of our repos, which is not great for maintenance.

[ernilambar]

Yes, .gherkin-lintrc is required as linter use rules mentioned in that file. I agree it should be placed somewhere in the central repo so that each command repo wont need it.

[swissspidy]

Then we put it in the .github repo and temporarily download it like you are already doing in this step here.

I would just download it to $RUNNER_TEMP

[ernilambar]

Completed in wp-cli/.github#127