NOTE: As a new user, I can’t share more than one link in my first post. So apologies for the lack of clickable links here
I absolutely love using GitHub Actions for my CI, though I’ve noticed a strange ghost in the machine that appears every now and then.
I have been working on building up a workflow file on my project, my workflow is triggered when I push to branches that have Pull Requests open against my default branch. I added a new step to a job in this commit
https://github.com/sgibson91/helm-upgrade/commit/5d06aed31747f5d0e9575a9ace1348f2e6fdd35e (full workflow file
https://github.com/sgibson91/helm-upgrade/blob/5d06aed31747f5d0e9575a9ace1348f2e6fdd35e/.github/workflows/ci.yml). However when I push, we can see in the logs
https://github.com/sgibson91/helm-upgrade/runs/914535256 that the step isn’t detected/run (we’re looking for the step name “Commit the edited metadata file”).
If I push a new commit (my next one was updating docs), then the checks successfully identifies the new step and runs it no problem - but I expected this to happen when the checks executed for the previous commit. Does anyone have any insight into why this might be happening?
Unfortunately, I don’t think this is a very reproducible problem, however it’s happened enough times that I’ve noticed it. Any info you may have would be very useful!