-
-
Notifications
You must be signed in to change notification settings - Fork 49
Description
Description
I have been using the action for a while. It has been working correctly so far.
However, I'm noticing many duplicate skips failing to apply recently.
Could there be something that changed on GitHub side that cause the action to fail at its job?
Example
Workflow: https://github.com/crim-ca/weaver/blob/master/.github/workflows/tests.yml
Runs:
They correspond to the same latest commit of the PR:
The first run (https://github.com/crim-ca/weaver/actions/runs/14719831540/job/41311332495) correctly detects that it should not skip.
The second run (https://github.com/crim-ca/weaver/actions/runs/14719831894/job/41311340938?pr=818) also correctly detects it should skip.
However, for whatever reason, it does not!
As highlighted below, the action detects that it should skip from the other run, but all the steps that depend on the skip-duplicate step keep going and execute.



