Automate your Pull Requests
Julien Danjou — Founder @ Mergify�GitHub Paris Meetup @ Doctolib
26th March 2019
The Process
Merge?
The Problem
The Solution
In Practice
pull_request_rules:
- name: automatic merge
conditions:
- '#approved-reviews-by>=2'
- status-success=Travis CI - PR
actions:
merge:
method: merge
No need to teach “merging rules” to your contributors:
.mergify.yml is your policy
Features
Delete Head Branch
Dismiss Review
Close
Comment
Merge
Label
Actions
Use Case: Automatic Backport
Merge
base=master
backport-to-prod
Backport
Copy
(backport)
Merge
Open
base=master
backport-to-prod
Merged
base=production
Open
base=production
Merged
Automatic Merge from Bots
pull_requests_rules:
- name: automatic merge
conditions:
- '#approved-reviews-by>=1'
- status-success=Travis CI
actions:
merge:
method: rebase
- name: backport to production
conditions:
- label=backport-to-prod
actions:
backport:
branches:
- production
- name: automerge production
conditions:
- author=mergify[bot]
- base=production
- status-success=Travis CI
actions:
merge:
method: rebase
Greenkeeper
Dependabot
Strict Workflow
PR#1
PR#2
PR#1
PR#2
master
Strict Workflow
PR#1
PR#2
PR#1
PR#2
Merge
Rebase
PR#1
pull_requests_rules:
- name: automatic merge
conditions:
- '#approved-reviews-by>=1'
- status-success=Travis CI
actions:
merge:
method: merge
strict: true
mergify.io