Christopher Dignam

@alita-moore I've deployed #785 to production, so you can enable the `merge.block_on_neutral_required_check_runs` setting (currently undocumented) to stop Kodiak from merging a PR if a required check run has a neutral...

Does this `merge.dont_wait_on_status_checks` setting work for your use case? https://kodiakhq.com/docs/config-reference#mergedont_wait_on_status_checks This way, if you have a status check that never finishes, like `WIP`, then you can specify that check in...

@alita-moore Kodiak always obeys GitHub Branch Protection, so if a status check is required, Kodiak won’t be able to merge the PR until it passes That setting I linked will...

Looking in the logs, Kodiak set the `not waiting for dont_wait_on_status_checks` status message at 19:38:25 ET, but the `EIP Auto-Merge Bot` was marked as successful at 19:37 ET. So I...

This isn't the normal Kodiak behavior. You shouldn't normally have this issue. Typically you will never have to futz with Kodiak, but when the GitHub Api flakes out, you may...

@alita-moore Yeah, I'm sure we could build a better solution. It's not something that we've invested in because it hasn't been that big of an issue. Currently Kodiak only evaluates...

I think this would be a great feature to have in Kodiak. That GitLab article has some nice information to work off. I need to do some more thinking about...

I've done some sketching and I think this is a reasonable feature to add. It's different from Kodiak's normal flow because Kodiak would be creating new branches and waiting on...

I think the basics for this aren't too difficult to implement using the GitLab blog post as an example. But there's an edge case that I'm not sure how to...

Maybe this new branch protection feature could allow us to bypass that branch protection problem? https://github.blog/changelog/2021-11-19-allow-bypassing-required-pull-requests/