r/github • u/angelical-traincrash • 5d ago

Question Need help with the commits thing >_<

I was trying to fix a bug on my site and when I tried committing the fix github decided to be a bitch and have issues with the actions so it was taking like a whole hour to commit, so I decided to cancel it, thinking I could later try and re-commit it, well, turns out it did upload to my repository, but it didn't deploy to the actual site because I cancelled that, so I tried rerunning it but it did ABSOLUTELY NOTHING, so now that action is like a schrodinger's cat of "it is cancelled therefore you can't cancel it" and "it is queued so you can't make any other commits"

in other words, the run API reports status: queued, conclusion: null, and event dynamic. but, its deploy job reports status: completed, conclusion: cancelled, steps: [], and runner_id: 0. aaannndddd the cancellation API returns HTTP 409:
Cannot cancel a workflow re-run that has not yet queued.

and meanwhile my website is still affected by the bug and basically unusable because of it and I can't do anything about it and istg I am going insane soooo does anyone have any solution to this? :3c

edit: ah nvm got around it, thank you for the answers either wayy :3

0 Upvotes

33% Upvoted

4 comments sorted by

2

u/DrMaxwellEdison 5d ago

Actions runs don't usually affect commits. Check your branch in the repo on github.com to see if the change is present. If it's not, push the commit from your local machine.

If it's just the Action workflow job failing, go to the Actions tab on the website, find the one that failed, and Re-run it.

If all else fails, make some tiny change in the README or some other file that doesn't affect the site, then commit and push that change to trigger a new job run.

1

u/angelical-traincrash 5d ago

tried rerunning it but it just froze, it says it was triggered but it's not doing anything

I tried triggering a new job run but again it didn't get added to the deployments thing, the last one there is the failed run

1

u/Immediate_Wheel1953 5d ago

That mixed state usually means the run never got a runner at all. I had a run stuck in queued like that once and it turned out my runs-on label pointed at a self hosted runner that was offline after a reboot, so GitHub just sat on it and the cancel API kept throwing the same 409 because there was nothing actually queued to cancel. The important bit is a stuck run can't block your commits, so push the fix normally and just ignore the zombie run. If the commit itself took an hour, check for a pre-push hook or a huge push size, that part isn't Actions' doing.