I've noticed this morning that none of my push events are triggering the actions workflow that has been working perfectly fine until now.
Is anyone else noticing this, and is there an issue with actions ongoing that we should be aware of?
Same here; was in the middle of testing a new workflow and now nothing happens when I commit. Looks like we'll have to wait until somebody fixes this.
Some insight into what is or is not happening would be nice.
Quick update. I've noticed a couple of my push actions being triggered, but only after about 15/20 mins.
Obviously an issue going on, and would benefit from an official Github answer on any known issue/activity that would cause this (especially as we're getting closer to go-live date with no current visible health status on actions).
For anyone else experiencing this, keep an eye out and see if you see a similar delay for the actions to be triggered,
I also met the following problem with the default GitHub checkout actions after the delayed triggering.
##[error]fatal: reference is not a tree: d6f20672a6adedd03f27f359040dcb4321e2fdb4 Removed matchers: 'checkout-git' ##[remove-matcher owner=checkout-git] ##[error]Git checkout failed with exit code: 128 ##[error]Exit code 1 returned from process: file name '/home/runner/runners/2.160.0/bin/Runner.PluginHost', arguments 'action "GitHub.Runner.Plugins.Repository.v1_0.CheckoutTask, Runner.Plugins"'.
My initial guess would be that because of the delayed notification, the sha ref of the specific commit / push that triggered your original activity is no longer available (ie due to additional changes in the repo between the original activity and the time when the action actually triggered etc).
Looks like this could be being caused by a noted degradation in the notifications capability noted in https://www.githubstatus.com/.
Its also affecting any external solution expected to see event webhook notifications for triggering builds etc.