Checked on my side, re-run failed workflow will still use the old workflow yaml.
I used ‘actions/checkout@ v3’ to fail the workflow, and update with v2 which is the correct version. Re-run failed workflow still use old yaml, screenshot as below:
It was failing on the step “Run actions/checkout@v2 - Fetching the repository”. The workflow file when it failed was this one. I actually re-ran multiple times before making changes to the workflow and the action always failed at that step. I then pushed a fix to master updating the workflow to this and re-ran the action which then ran correctly.
Is there a way I can access the logs of the previous re-runs?
Thanks for your reply! The failed workflow yaml has same commit/tree ID with the fixed one, looks them are identical. Could you please let me know what did you fix?
And can you reproduce on your workflow now? the checkrun id is different between the failed workflow and re-run workflow, so you can record the id for comparison.
If it cannot be reproduced, i assume it could be a temporary problem.
I have the same issue; changes to my workflow file are not honored at all.
Additionally, I cannot cancel the workflow! (See: Can't cancel github action workflow)
If I recall correctly they run based on what was in the the branch you branch from at the time the branch was created. (So if you create a feature branch from master 3 days ago, it’ll run the workflows from 3 days ago when you PR.) So if you update master and want it in your PR then you need to rebase and force push.
Exactly. It’s very annoying that re-run does not use the updated workflow file. For example, if the workflow triggers on release, once has to create a new release just to debug the workflow. This is highly inconvenient.
+1 for this feature.
I tried adding workflow_dispatch: to my workflow yml file, but alas, cannot find a button to manually run checks for a PR anywhere. @ASarco Do you have any more details?
if I had updated my workflow yml, how to be able to run checks for a PR which will use the updated configuration?
Just run into this issue myself. Doing on on-release action, realized that I forgot to tell it to add some static files to the archives, updated the yaml, re-released, it’s still using the old yaml.
Anyone figure out a solution to this? Re-running the workflow manually as @ASarco suggested just simply re-runs it using the old workflow file, not the new one like we’re trying to accomplish.