Skip to content
This repository has been archived by the owner on May 4, 2022. It is now read-only.

Latest commit

 

History

History
42 lines (29 loc) · 3.7 KB

INFO.md

File metadata and controls

42 lines (29 loc) · 3.7 KB

Never wait on someone to merge a pull requests again! With this skill you can automatically merge pull requests on GitHub based on assigned labels. Required reviews and checks settings configured in the repository on GitHub are used as the rules for auto-merging.

This approach makes it easy for pull request authors (or anyone with permissions in the repository) to flag a pull request for auto-merge, as well as set the merge option, simply by adding a label. The merge option can also be set with a label on the pull request.

When a new pull request is created, this skill will automatically apply the default auto-merge policy and method labels (if set). The labels can be changed on the pull request to modify the policy or merge method for auto-merge.

Opting out of auto-merge is a simple matter of removing the auto-merge labels from a pull request.

Once the requirements for auto-merging have been met, the pull request will be merged with the merge method defined for the pull request.

Auto-merge behavior is managed using easily visible labels

For every new pull request raised, this skill automatically applies the relevant labels to control the merge policy and merge method.

  • Auto-merge policy labels

    • auto-merge:on-approve
    • auto-merge:on-check-success
    • auto-merge:on-bpr-success
  • Auto-merge method labels

    • auto-merge-method:merge
    • auto-merge-method:rebase
    • auto-merge-method:squash

Pull request labels

Auto-merging after policy is satisfied

Auto-merge