Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add PR merge automation using [Mergify](https://docs.mergify.com). This configuration is similar to merge automation enabled on the `instructlab/instructlab` and `instructlab/instructlab-bot` github repositories. While it is still possible to merge by hand, the intent of this automation is merge things automatically once they meet specified criteria. This should be able to handle merges the vast majority of the time. Some exceptions include, but aren't limited to: - Changes to the mergify config (these won't get auto merged) - Changes to fix something urgently broken - Dealing with various infrastructure outages Mergify has a very flexible configuration for defining merge policy. The configuration proposed here includes: - Require approvals from 2 maintainers - There are no outstanding review requests. For example, if someone requests review from a specific person, the PR will not get merged automatically until that review is given or the review request is dismissed. - There are no "changes requested" reviews still pending. If a past review requested changes, the PR will not get automatically merged until that person reviews again. - There are no prohibited labels set on the PR, including `hold`, `do-not-merge`, or `needs-rebase`. - Expected CI jobs are all passing. This is the most verbose part of the configuration, because we have to define when we expect the CI job and when we don't. This is based on what files changed, and the pattern list must stay in sync with the github workflow configuration. On any given PR, you can check on Mergify's analysis of the PR against the merge criteria by clicking the `Details` link next to Mergify's line item in the list of checks - the same place where CI results show up. Signed-off-by: Russell Bryant <[email protected]>
- Loading branch information