Appearance
How it works
For an eligible pull request, EasyMerge follows this flow.
From push to comments
- 1Trigger
Open or update a pull request
GitHub sends the selected pull request event to EasyMerge.
- 2Eligibility
Apply repository rules
Repository settings and .easymerge.yaml decide whether and how the review runs.
- 3Review
Understand the change
EasyMerge uses the pull request context and review configuration to assess the change.
- 4Progress
Findings appear live
The dashboard updates while the EasyMerge Review check is running.
- 5Result
Read one GitHub review
You get a recommendation, summary, merge confidence and inline findings.
Draft pull requestWaits until it is ready for review
Event or filter says skipCheck closes as Review skipped
New commit or closed pull requestThe current review is cancelled
Excluded files and files without a GitHub diff are left out. A completed run results in one review on GitHub when posting is enabled.
Next
- Quickstart; install the GitHub App and trigger your first review.
- Your first review; read the result on GitHub and in the dashboard.
- Review lifecycle; triggers, statuses and cancelled runs.