FWIW, I added an 'empty' commit to force the CI. I'm still wondering if there's a better way, but for future explorers that might help.
git commit --allow-empty -m "Trigger CI" On Tuesday, 16 July 2019 12:42:56 UTC-5, d-little wrote: > > The Shippable CI failed on one of my PR's with the following errors: > > 00:01 ERROR: Commit ae0ff3dc1819347652cab7589f26ca9339c7e5f9 was not found: > 00:01 > 00:01 fatal: bad object ae0ff3dc1819347652cab7589f26ca9339c7e5f9 > 00:01 > 00:01 GitHub may not have fully replicated the commit across their > infrastructure. > 00:01 It is also possible the commit was removed by a force push between > job creation and execution. > 00:01 Find the latest run for the pull request and restart failed jobs as > needed. > > > It definitely looks like the commit did not get replicated before this > Shippable task ran. Is it possible to force checks to be re-run without > submitting a do-nothing commit to the branch? > > > *PR #59112* - https://github.com/ansible/ansible/pull/59112 > *Shippable #132310* - > https://app.shippable.com/github/ansible/ansible/runs/132310 > > > Thanks! > -- You received this message because you are subscribed to the Google Groups "Ansible Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-devel/762e2aa8-ec91-46fa-bfd5-fda3d7a529c4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
