Does re-running a failed job use the latest workflow file? #27083
-
I have a failed CI job. I have since updated its workflow file in a new commit. If I do “re-run jobs” will it use the workflow file at HEAD or will it re-run with the original workflow file? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
It will use the original workflow file. For re-runs we try to keep the resources used same. With one caveat, if the workflow uses some actions at a version, if that version was force pushed/updated, we will be fetching the latest version there. |
Beta Was this translation helpful? Give feedback.
-
I have a similar problem. I'm using a reusable workflow and one of my job failed because there is an error on the reusable workflow file. If I commit the change in the called workflow and then This is my workflow: name: Release
on:
push:
branches:
- main
jobs:
release:
uses: my-org/wl-reusable-workflows/.github/workflows/release.yml@main
secrets: inherit |
Beta Was this translation helpful? Give feedback.
-
I have a similar use case. I've create a new branch with a new workflow.yml file and opened a PR. Now, I'm making changes on that yml file, and updating opened PR. When re-running workflow it uses a SHA from base commit, which ends up re-running obsolete .yml. Is there a possibility to re-run workflow for head SHA ? |
Beta Was this translation helpful? Give feedback.
It will use the original workflow file. For re-runs we try to keep the resources used same. With one caveat, if the workflow uses some actions at a version, if that version was force pushed/updated, we will be fetching the latest version there.