Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Build: Remove spider-check trigger from new branches/tags
The `paths` filter isn't just about commits that add or modify files, GitHub seemingly also triggers this for any new tags and new branches that inherit from existing commits/branches where these files already exist, even if the new branch/tag does not add or modify these files at all. This seems like a bug, but is sufficiently annoying (especially on older 2.x-related branches) that it's better to turn off in favour of manual workflow_dispatch for the rare case where I want to test this before a given commit is merged to main.
- Loading branch information