Pull request doesnot show: There are no merge-conflicts

[dpakprajul]

Discussion Type

Product Feedback

Discussion Content

When I create a pull request, previously github used to check the conflict present. If not, it showed in green font: There are no merge conflict. And if there would be conflict, it would show us in red font. But now when I make a pull request, I cannot see anything of these. Has GitHub changed its thing?

[mecodeatlas]

Thanks for posting in the GitHub Community, @dpakprajul!

We're happy you're here. You are more likely to get a useful response if you are posting your question in the applicable category, the Discussions category is solely related to conversations around the GitHub product Discussions. This question should be in the Pull Requests category. I've gone ahead and moved it for you. Good luck!

[savin000]

Hi!
In the created pull request you should see something like this:

[Aavtic]

Yeah, I’ve noticed that too recently and totally get what you mean.

GitHub still shows the merge conflict status, but sometimes it takes a few seconds to appear — especially right after creating the pull request. If it's not showing up right away, try refreshing the page or clicking into the "Files changed" tab; that usually triggers it to update.

Also, if the PR is coming from a fork or if there are certain branch protection rules in place, GitHub might not run that automatic check immediately, or might defer it to CI instead.

So no, GitHub hasn’t removed the feature — it’s just being a bit shy sometimes 😅

Hope that helps! Let me know if it’s still not showing up for you even after a refresh.

[codedbysoumyajit]

Hey! Yeah, I’ve noticed that too recently — looks like GitHub tweaked the PR UI a bit. Sometimes the mergeability info (like “No conflicts” in green or conflict warnings) takes a few seconds to load, or it shows up under the “Merge” dropdown instead of right at the top.

If it’s missing completely, it might also be a temporary glitch or something related to the repo’s branch protection settings. Try refreshing the page after a few seconds — that usually does the trick for me.

Hope that helps!

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[PRIYAtechky]

GitHub recently updated the pull request interface, and the explicit green/red conflict status messages you mentioned are no longer always displayed in the same way.

Instead:

• If there are no conflicts, GitHub generally just shows the merge option (e.g., “Merge pull request”) without the old green confirmation text.
• If there are conflicts, you’ll still see a warning banner indicating that the branch has conflicts that must be resolved before merging.

This is a UI/UX change rather than a removal of functionality. The conflict detection is still performed, but the way it’s communicated has been streamlined in the latest GitHub interface.

[tanmaygalav]

GitHub has not removed the merge conflict check. Only difference is, now it does not show in the compare screen. When you click “Create pull request” and open the PR, GitHub will run the check and show either “This branch has no conflicts with the base branch” in green or “This branch has conflicts that must be resolved” in red. This change was made because the status can change if new commits come in the base branch, so GitHub shows it inside the PR instead of the compare page.

[joelwatson]

Understood, but having the conflict status for the snapshot of the diff when creating the PR is SUPER helpful in reducing unwanted PRs. For example, I have a repository that often has conflicts for one particular file. Prior to this "update", GitHub would alert about the conflict before I created the PR, and I could then create my own PR locally and push it up when needed.

With the change, however, I only ever know if the PR will be in a conflicted state AFTER creating it, which basically makes using GitHub to create PRs for this particular repo nearly pointless.

It's very annoying...I get that it probably saves Microsoft some money in not allocating compute to every single potential PR, but holy crap it makes the interface about 3000x more frustrating to use.