Yes, yes and yes. We had this issue on the Neovim project a while ago [1]. This caused us to switch workflows [2] (although I would have preferred the --exec ap

Yes, yes and yes. We had this issue on the Neovim project a while ago [1]. This caused us to switch workflows [2] (although I would have preferred the --exec approach that you mentioned). Also see comment [3] by TheCorey mentioning you can use `git bisect --skip`. However, in the mentioned case with Neovim, very few commits actually built, making the process non-deterministic somehow (it kept going in cycles). [1]: https://github.com/neovim/neovim/issues/6431 https://github.com/neovim/neovim/issues/6431 [2]: https://github.com/neovim/neovim/issues/6435 https://github.com/neovim/neovim/issues/6435 [3]: https://news.ycombinator.com/item?id=15264159 https://news.ycombinator.com/item?id=15264159