Skip to content

Commit

Permalink
Build: Remove spider-check trigger from new branches/tags
Browse files Browse the repository at this point in the history
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
Krinkle committed Dec 3, 2024
1 parent 8f096e9 commit 05dbbfd
Showing 1 changed file with 0 additions and 7 deletions.
7 changes: 0 additions & 7 deletions .github/workflows/spider-check.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -5,13 +5,6 @@ on:
- cron: '0 0 * * 5'
# Or manually
workflow_dispatch:
# Or when developing this workflow
push:
paths:
- .github/workflows/spider-check.yaml
pull_request:
paths:
- .github/workflows/spider-check.yaml

jobs:
spider-check:
Expand Down

0 comments on commit 05dbbfd

Please sign in to comment.