Keypup

Dataset: Issues &amp; Pull Requests

Description: The mergeability state of the pull request. Possible values are:

<code>MERGEABLE</code> the pull request can be safely merged

<code>CONFLICTING</code> the pull request conflicts with the base branch

<code>UNKNOWN</code> the mergeability state cannot be evaluated or is being evaluated

- <code>MERGEABLE</code> the pull request can be safely merged
- <code>CONFLICTING</code> the pull request conflicts with the base branch
- <code>UNKNOWN</code> the mergeability state cannot be evaluated or is being evaluated

The <code>Mergeable</code> field is a vital, real-time indicator of a pull request's health, allowing you to proactively identify and manage integration blockers. Its primary use is for filtering and creating high-level KPIs to monitor the overall health of your development pipeline.

Filtering for Immediate Action: You can create actionable lists that help developers prioritize their work and keep the pipeline flowing.

- Find Conflicting PRs: The most critical use case is to build a report of all open pull requests that need immediate attention by using a filter like <code>Mergeable = "CONFLICTING"</code>. This allows developers to resolve conflicts before the branch diverges too far from the base.
- Create a "Ready to Merge" Queue: You can identify pull requests that are fully ready for deployment by combining filters to ensure they meet all criteria: <code>Mergeable = "MERGEABLE" and Review State = "APPROVED" and Build Status = "SUCCESS"</code>.

Reporting on Pipeline Health: Using <code>Mergeable</code> as a dimension gives you a high-level snapshot of the state of your open pull requests.

- A pie chart with <code>Mergeable</code> as the dimension and <code>COUNT()</code> as the metric can instantly show you the proportion of your open work that is healthy, blocked by conflicts, or in an unknown state.

Custom Formulas for Trend Analysis: You can track the health of your branching and integration strategy over time by creating targeted KPIs.

- Conflict Rate: Monitor the percentage of open pull requests that are conflicting with a custom formula like <code>ROUND(COUNT_IF(mergeable == "CONFLICTING") / COUNT() * 100, 2)</code>. A rising trend in this metric can be an early warning sign that your feature branches are too long-lived or that your team needs to rebase more frequently.

- Filtering for Immediate Action: You can create actionable lists that help developers prioritize their work and keep the pipeline flowing.
 - Find Conflicting PRs: The most critical use case is to build a report of all open pull requests that need immediate attention by using a filter like <code>Mergeable = "CONFLICTING"</code>. This allows developers to resolve conflicts before the branch diverges too far from the base.
 - Create a "Ready to Merge" Queue: You can identify pull requests that are fully ready for deployment by combining filters to ensure they meet all criteria: <code>Mergeable = "MERGEABLE" and Review State = "APPROVED" and Build Status = "SUCCESS"</code>.
- Reporting on Pipeline Health: Using <code>Mergeable</code> as a dimension gives you a high-level snapshot of the state of your open pull requests.
 - A pie chart with <code>Mergeable</code> as the dimension and <code>COUNT()</code> as the metric can instantly show you the proportion of your open work that is healthy, blocked by conflicts, or in an unknown state.
- Custom Formulas for Trend Analysis: You can track the health of your branching and integration strategy over time by creating targeted KPIs.
 - Conflict Rate: Monitor the percentage of open pull requests that are conflicting with a custom formula like <code>ROUND(COUNT_IF(mergeable == "CONFLICTING") / COUNT() * 100, 2)</code>. A rising trend in this metric can be an early warning sign that your feature branches are too long-lived or that your team needs to rebase more frequently.

Issues and PRs > Mergeability

Find answers and get help from Intercom Support and Community Experts

This site employs cookies and other technologies that we and our third party vendors use to monitor and record personal information about you and your interactions with the site (including content viewed, cursor movements, screen recordings, and chat contents) for the purposes described in our Cookie Policy. By continuing to visit our site, you agree to our {websiteTermsLink}, {privacyPolicyLink} and {cookiePolicyLink}.

This site uses cookies and similar technologies ("cookies") as strictly necessary for site operation. We and our partners also would like to set additional cookies to enable site performance analytics, functionality, advertising and social media features. See our {cookiePolicyLink} for details. You can change your cookie preferences in our Cookie Settings.

We use cookies to make our site work and also for analytics and advertising purposes. You can enable or disable optional cookies as desired. See our {cookiePolicyLink} for more details.

Advertising cookies are set by our advertising partners to collect information about your use of the site, our communications, and other online services over time and with different browsers and devices. They use this information to show you ads online that they think will interest you and measure the ads' performance. Social media cookies are set by social media platforms to enable you to share content on those platforms, and are capable of tracking information about your activity across other online services for use as described in their privacy policies.

These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.

These cookies are necessary for the website to function and cannot be switched off in our systems.

These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site.

You have the right to opt out of the sale of your personal information. See our {cookiePolicyLink} for more details about how we use your data.

Your Privacy Choices

We use cookies to enhance your experience. You can customize your cookie preferences below. See our {cookiePolicyLink} for more details.

Cookie Settings

Link, Press control-option-right-arrow to exit

Empty Help Center

Uh oh. That page doesn’t exist.

Disappointed

Neutral

Smiley

Thinking...

Searching through sources...

Analyzing...

Tickets submitted through the messenger or by a support agent in your conversation will appear here.

From:
Github (PRs, Issues)	`mergeable`: `MERGEABLE` `CONFLICTING` `UNKNOWN`
Gitlab (PRs, Issues)	`merge_status`: `can_be_merged` => `MERGEABLE` `unchecked` => `UNKNOWN` `cannot_be_merged` => `CONFLICTING`
Bitbucket (PRs, Issues)	Evaluated using the merge status of each file in diffstats.files: `All are mergeable` => `MERGEABLE` `One is not mergeable` => `CONFLICTING` `Diffstat not available` => `UNKNOWN`
Azure DevOps (PRs, Issues)	`mergeStatus`: `conflicts` => `CONFLICTING` `failure` => `CONFLICTING` `notSet` => `UNKNOWN` `queued` => `UNKNOWN` `rejectedByPolicy` => `CONFLICTING` `succeeded` => `MERGEABLE`
JIRA (Issues)	N/A
ClickUp (Issues)	N/A
Trello (Issues)	N/A

Issues and PRs > Mergeability

Reporting Use Cases