GitHub Community
[BUG] Manual Actions runs with workflow_dispatch always checks out a tree one commit out of date
#26071
-
|
I’m using Github Actions with my project for CI and automation, and I was particularly excited to use the newly-announced See here for an example of the problem. In this case, I’d submitted a patch to fix a bug we’d uncovered in an Actions run. However, after my colleague initiated a manual run with What’s even stranger is that the exact same code and the exact same commit ran perfectly once it hit a scheduled re-run. The only conclusion I can draw is that Actions’ |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
|
I’m probably missing something, but which part of this workflow checks out the code from the rest of your repository? I’m not really familiar with nginx, but I don’t think running a workflow_dispatch or other workflow automatically checks out your whole repository, does it? I have @actions/checkout in all of my workflows, but maybe you’re updating the files in some other way? How do they get into Edit: I see you are pulling a container that copies some stuff into |
Beta Was this translation helpful? Give feedback.
-
|
Hi @mbestavros, To confirm the commit info with ‘workflow_dispatch’, i created a simple yaml as below: Edit the test.txt(commit Hence, it seems that in your yaml code, you didn’t pull the correct content. Thanks. |
Beta Was this translation helpful? Give feedback.
-
|
@weide-zhou Thanks for your help! It turned out it wasn’t a bug with Actions, but rather my setup: The scripts that were running with a delay were included as part of a container image that was only rebuilt when I pushed to master. So when I reran it on a different branch, I wasn’t actually using updated code. Apologies for the confusion! |
Beta Was this translation helpful? Give feedback.
@weide-zhou Thanks for your help! It turned out it wasn’t a bug with Actions, but rather my setup:
The scripts that were running with a delay were included as part of a container image that was only rebuilt when I pushed to master. So when I reran it on a different branch, I wasn’t actually using updated code. Apologies for the confusion!