Drop the eslint job, which could never have passed here
This plugin ships no JavaScript: no js/ directory, no scripts, no
package.json. The workflow carried a "JS coding standards and tests" job
anyway, and it did not fail at the linter -- it never reached one. It died
at actions/setup-node, looking for a lock file:
Dependencies lock file is not found in /home/runner/work/...
Supported file patterns: package-lock.json, npm-shrinkwrap.json, yarn.lock
A job that cannot pass is worse than no job. It puts a red mark on every
push for a reason nobody can act on, and teaches everyone to stop reading
the marks.
The shared standard said "a plugin with no js/ directory deletes the whole
eslint job". This plugin has no js/ directory, so the job should have gone
when the workflow was written; the check that compares a workflow to the
template was tolerating its absence rather than requiring it, so nothing
noticed either way.