Christopher Dignam

You could configure a GitHub Action to add a second approval. You could check if the pr is a dependabot PR and add an approval if so.

I think this is less of a Kodiak question and more of a continuous integration (CI) question. I think with GitHub Actions or CircleCI you can configure CI jobs to...

Yes, assuming you configure your CI provider to run CI jobs on certain branches, Kodiak will support that

Hey @styfle, Thanks for the suggestion! On a [separate project](https://github.com/sbdchd/squawk), we ran into a similar issue with GitHub Actions when using the ["on.push.paths" configuration option](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore). As a workaround, we're using...

One catch I just realized is that the [GitHub API](https://docs.github.com/en/graphql/reference/objects#branchprotectionrule) only provides a list of required status checks, not optional status checks. So there isn't a way for Kodiak to...

@etiennetremel It looks the CI job for building the bot container failed. Should be good to merge once that's fixed

Hey @charliegroll, this sounds like a nice enhancement! Prioritized merges should help during an incident. When you add the priority label to a PR, if there is a PR being...

@charliegroll Do you think the mergefreeze app would work for your use case or do you think this would be better as a part of Kodiak?

I think this current behavior is correct, but we could add this as an enhancement. GitHub considers "skipped" checks as passing. If you want to block merging if a check...

@alita-moore Maybe this will help for your use case? https://github.com/chdsbd/kodiak/issues/719#issuecomment-912681682 I think the https://github.com/technote-space/workflow-conclusion-action action can be used to fail the build if the conclusion of some jobs is failure