The "Check Lockfile" workflow had a paths filter
in the trigger, to only run when package-lock.json
is modified. Unfortunately there is an edge-case,
where package-lock.json is modified, and the
lockfile changes check posts a comment, and then
the package-lock.json changes are reverted, but
the lockfile changes check does not run again,
because now the PR has no updates to
package-lock.json.
This workflow is very fast compared with the other
checks in the repo, so I think it's ok to run for
every PR sync event.
The "Check Lockfile" workflow had a paths filter in the trigger, to only run when package-lock.json is modified. Unfortunately there is an edge-case, where package-lock.json is modified, and the lockfile changes check posts a comment, and then the package-lock.json changes are reverted, but the lockfile changes check does not run again, because now the PR has no updates to
package-lock.json.This workflow is very fast compared with the other checks in the repo, so I think it's ok to run for every PR sync event.