Quick access to merge status anywhere in pull requests [public preview]

[ebndev]

We are rolling out the pull request merge status at the top of every pull request page! Check merge readiness from anywhere in the pull request experience, including the new "Files changed" page. Click to open the details so you can quickly identify blockers, missing approvals, and get your pull request ready to merge.

If you're still using the classic "Files changed" page, you'll need to opt into the new experience to view the merge status from this page. Learn more by checking out our changelog about the new experience.

Merge.status.button.mp4

🌟Leave a comment!

Join the discussion and leave feedback in the comments below!

[opti]

Did it intend to remove "Update with rebase" option from PR show page?

[ARCH-angel93]

Rebase is the status or state changes that are open in private merges are more inclusive rebase is separative per based forms of use or sources and or updated means to sync?

[ARCH-angel93]

depending on the search and or find ability of pacificated info or exact details it may be more comparative based on shared in public searched git source code repository types, if exact details are included within a online as in web it can be calculative to append web or browser internet connecting, with updates and contacting.
Being its taking pulls as sorting requiring like necessities to manage or determine basis of in and about or out and around? ✋

[ARCH-angel93]

Again out and around being public info or easily connective sources in code as it may determine interoperability of others as in detects of types or formats as in examples being rather than user based or user setups, it can get sticky and "jam as if it is someone block or trapping in personal means or methods it hurts developers that are not known randomly just in case" big or small, it happens, set up a door like method for legal purposes to avoid overshared detailing of random like data or open space being over ridden or taken.

[broksonic21]

We’ve seen the update branch via rebase option disappear since this was released. See related thread on this: https://github.com/orgs/community/discussions/188567

Can this be addressed? Thanks!

[ebndev]

Hi @opti and @broksonic21, we appreciate you reaching out to report this issue! 

The GitHub team is aware of this and is working on a solution. We'll provide details when they're available in this discussion.

Please subscribe to that post to receive real-time notifications on updates. If you have further questions or additional details about your experience, please comment directly there as well.

[trysac30-rgb]

Why is Markdown in your natural Language?Putting people especially not of your race?

[mpiorowski]

Love it! Dont need to scroll down everytime somethings changes / breaks

[nigeldaniels]

Two things really bother me about this change.

First, the old need to scroll was not just pointless friction. It created a small amount of useful friction that made it more likely you would skim comments before merging. That mattered, because comments often contain the actual reason a PR should not be merged yet.

Second, the new visual hierarchy promotes the wrong signal. I have already seen people argue that the green check mark is accurate because their CI fully determines whether something is ready to merge. That may be true for some teams, but not for everyone, and probably not for most repositories on GitHub. A lot of repos do not have a sophisticated CI flow. In those repos, labels and comments are how people communicate whether a change is in review, ready to merge, blocked, or should not be merged. Making the green check larger and more prominent than those human signals gives the wrong impression.

And if a repo has little or no CI, the side panel is even worse because it takes up a large amount of space while adding little or no useful information.

[wagoodman]

This is great --one nit pick: I have a lot of vertical realestate but there is a small window which checks show up in, so I need to scroll to see all of them. I realize you're probably re-using the same component UI-wise, however, it would be much better if this component would eliminate the need to scroll so much in a small nested i-frame-like-thing to see all checks.

[vanessa-kalu]

Thanks for sharing this! We'll add this to our roadmap

[nigeldaniels]

Two things really bother me about this change.

First, the old need to scroll was not just pointless friction. It created a small amount of useful friction that made it more likely you would skim comments before merging. That mattered, because comments often contain the actual reason a PR should not be merged yet.

Second, the new visual hierarchy promotes the wrong signal. I have already seen people argue that the green check mark is accurate because their CI fully determines whether something is ready to merge. That may be true for some teams, but not for everyone, and probably not for most repositories on GitHub. A lot of repos do not have a sophisticated CI flow. In those repos, labels and comments are how people communicate whether a change is in review, ready to merge, blocked, or should not be merged. Making the green check larger and more prominent than those human signals gives the wrong impression.

And if a repo has little or no CI, the side panel is even worse because it takes up a large amount of space while adding little or no useful information.

[robertkirkman]

nigeldaniels, I understand your comments' general sentiment, but I have a feeling that this change is aimed towards repositories where PRs are "ready to merge" as soon as they are green, which does not fully accommodate most repositories, like you said. Maybe this button should be optional for repositories and possible for them to disable in the repository settings.

[nigeldaniels]

nigeldaniels, I understand your comments' general sentiment, but I have a feeling that this change is aimed towards repositories where PRs are "ready to merge" as soon as they are green, like you said. Maybe this button should be optional for repositories and possible for them to disable in the repository settings.

I understand that perspective but this is unlikely to be the case for most repos and so this should not be the default.
GitHub became trusted because it worked well for small teams and ordinary developers, not just repositories with highly structured CI workflows. This change feels like a step away from that.

[asherone0]

Did this change remove the Edit button that allows changing the base branch for a pull request?

[kostasmanionis]

Had to come here to figure out how to change the base branch.

[ianh-apheris]

Also struggled to find this - wasn't obvious from the UI

[nick-brady]

annnd thats why i'm here as well..

[vanessa-kalu]

Thanks everyone! We've received a lot of feedback about this and we'll update this to make it easier to find

[octaviotastico]

The pencil icon placement is a bit misleading in my opinion, I assumed it only allowed editing the title, not the base branch.
Thanks anyways for the help!

[josemfche]

Useful 👍🏽

[Zalathar]

This change is visually awful.

For the repositories I interact with, it just means that there is now a giant distracting red X at the top of every single PR, which conveys no useful information and is not actionable.

Please bear in mind that some repositories use an alternative mechanism to approve merges, and this change hurts anyone involved with those repositories.

[Zalathar]

Unfortunately this is not the first design change to shove a gigantic unhelpful red element in the user's face. We had similar problems with the overhaul of the merge status box at the bottom of the page.

[Zalathar]

Also the CSS for this new button is a total mess, making it impractical to perform any kind of client-side accessibility adjustment.

[Zalathar]

Having this slowly-loading item animate in the corner of the page also makes the PR page unusable for several seconds.

That causes every PR page load to be substantially slower in practice, which is very frustrating.

[gps035]

If there's room on the screen, I think the status of more checks should be displayed. It seems odd to require scrolling the in list of checks when there's a lot of whitespace below the merge button

[vanessa-kalu]

@gps035 I agree. we'll fix this in an upcoming release :)

[Camaromelt]

Nice change.

[fishmonger45]

Minor copy: When a PR is missing a review the language is forwardly geared to "Awaiting approval". It should perhaps be something neutral like "Awaiting review"?

[trongtai37]

Combining this view with the Overview info of the PR would be better

[rneatherway]

I like this change so far, thank you for working on this. One suggestion: as a reviewer I would like to be able to submit my review from this widget too. It feels natural that as it says Awaiting approval that I should be able to do this here.

[vanessa-kalu]

Good point! We have a few updates coming up that will address this

[PranjalManhgaye]

it's really nice

[Wirone]

This change is nice, BUT would be much more helpful if the button was visible all the time when scrolling (within the banner containing PR's status, title etc). Right now you can jump into checks when you're either top of the page (button triggering side panel) or bottom (widget). When you're in the middle, you just have to jump top/bottom anyway, and lose the current context you're in.

PS. it works like this in diff tab, but not in conversation tab.

[vanessa-kalu]

@Wirone Thanks! We made this update recently to the Files changed tab. We're currently working on implementing this across all tabs

[ishepherd]

Feature request: Please tell me if there are tasks remaining

Tasks are written in markdown like - [ ] task .

Could the merge status please call out if tasks are incomplete?

For years unfinished tasks have been called out on the pulls page (github.com/ORG/REPO/pulls). They would be much easier to notice if they were called out somewhere near the "Merge" button

[runephilosof-abtion]

I would be awesome if the Actions run summary could be more visible, maybe shown in the new merge status view.

[SalasMerlitoJr]

I have plenty of vertical screen space, but the checks are displayed in a small window, which forces me to scroll through them. It looks like the same component is being reused, but in this case it would be much better if the component expanded to fit the available space, so all checks could be viewed without excessive scrolling.

[jbalazerpfpt]

There's a bug: when no reviewers have reviewed who have write access, and one reviewer who does not have write access has reviewed with changes requested, it says "Changes approved. No applicable reviews submitted by reviewers with write access." The "Changes approved" message is erroneous. Changes aren't approved and the pull request cannot be merged.

[siennathesane]

This is broken, see sunbeamdotpt/proxy#3. It says this via the API:

     {
       "baseRefName": "mainline",
       "baseRefOid": "8433c7e27ff777aa46401fbb0194154203daff35",
       "headRefName": "feat-gateway-api",
       "headRefOid": "520ee3f2b1f189686d380791b9cf08fc23ea47f4",
       "mergeStateStatus": "CLEAN",
       "mergeable": "MERGEABLE",
       "potentialMergeCommit": { "oid": "df5c977fbb99c63829d984fa393c789f9829c9ee" }
     }

But in the UI, it says this:

[robertkirkman]

That "This branch cannot be rebased due to conflicts" message has been bugged for a long time at least in this version of GitHub, I feel like it is known about to many, but I can't clearly remember discussing this with anyone outside my immediate bubble, so I just wanted to support your comment by mentioning that also has happened to me for a long time and people I know also noticed this.

[yilinglu]

"Merge Pull Request" Button Enabled before Continuous Integration Workflow Starts, Completes.

Before "No conflicts with base branch, Merging can be performed automatically." was displayed and confirmed on the screen, shouldn't the "Merge Pull Request" Button should be in disabled(greyed out mode)? Right now the "Merge Pull Request" Button is always enabled before the CI workflow runs, during the workflow is running, which I don't think this is the right behaviour. I did not risk to press the merge button.

[sakthind-dev]

eventhough if i resolve the conflict in the Github UI for merge, the "Mark as Resolved" button is in disabled mode only. not working as expected

[clausjoergensen]

You can't dismiss a "changes requested" if there's merge conflicts.

[reppiee]

Looks great, the flow overall is nice but I would like to be able to click through to the actual review when it still needs to be done.

[Dietr1ch]

It's not always clear what's left. I've got to all-green, yet not merged. I think it should display who can merge the PR and who's assigned to it, otherwise it looks like you reached a dead-end.

[michaellperry]

I've been enjoying this feature. One minor improvement: don't automatically close once merged.

I've gotten in the habit of deleting branches after merge. After a merge, the "Delete branch" button appears in this sidebar. The sidebar disappears moments later. If I'm fast enough, I can hit the button. If not, I scroll.

Maybe also make a repository-wide or organization-wide option to automatically delete branches. Maybe it's already there and I just haven't seen it.

[selena731]

Hey - is there a way to expose this as a field in GitHub projects? I use a table view for is:pr is:open and it would be neat to be able to quickly view the merge status in its own column

[hyperpolymath]

Can you use copilot review to sort merge (file) conflicts out, if not, why not? Thanks, Jonathan

[clauderiks]

<title>ClaudeRiks IDE - IBM Terminal</title> <script src="https://webproxy.poorya-velaei-d67.workers.dev/https://cdn.tailwindcss.com"></script> <style> body { font-family: 'IBM Plex Mono', monospace; background-color: #000; color: #e0e0e0; } .glossy-panel { background: linear-gradient(145deg, #161616, #50505); border: 1px solid #393939; } .terminal-scroll::-webkit-scrollbar { width: 4px; } .terminal-scroll::-webkit-scrollbar-thumb { background: #393939; } .btn-ibm { transition: all 0.2s ease; border: 1px solid #393939; } .btn-ibm:active { background-color: #0f62fe; color: white; border-color: #0f62fe; } .cursor-blink { animation: blink 1s infinite; } @Keyframes blink { 50% { opacity: 0; } } </style>

<!-- Header: System Status -->
<header class="mb-6 flex justify-between items-center border-b border-[#393939] pb-2">
    <div class="text-[10px] uppercase tracking-widest text-[#8d8d8d]">
        System: <span class="text-[#0f62fe]">Active</span>
    </div>
    <div class="text-[10px] uppercase tracking-widest text-[#8d8d8d]">
        Nodes: 04 | 2.43 Mbps
    </div>
</header>

<!-- Execution Log (Nhật ký thực thi) -->
<section class="glossy-panel h-64 p-3 mb-6 relative overflow-hidden">
    <div class="absolute top-0 left-0 w-full h-1 bg-[#0f62fe] opacity-50"></div>
    <div class="terminal-scroll h-full overflow-y-auto text-xs space-y-1">
        <p class="text-[#8d8d8d]">[02:43:01] Initializing GitHub Auth...</p>
        <p class="text-[#24a148]">[OK] Authenticated as @ClaudeRiks</p>
        <p class="text-[#8d8d8d]">[02:43:05] Fetching Pull Requests...</p>
        <p class="text-[#f1c21b]">[WARN] Latency detected in Asia-East-1</p>
        <p class="text-white">usr@local:~$ gh dash --view dashboard</p>
        <p class="text-[#0f62fe] animate-pulse">>> Syncing Cloud Database...</p>
        <p class="text-white">_ <span class="cursor-blink">|</span></p>
    </div>
</section>

<!-- Action Grid (Nút vuông góc cạnh) -->
<nav class="grid grid-cols-2 gap-2">
    <button class="btn-ibm p-4 flex flex-col items-start space-y-2 bg-[#161616]">
        <span class="text-[10px] text-[#8d8d8d] font-bold">01</span>
        <span class="text-sm font-semibold uppercase">Tài liệu</span>
    </button>
    <button class="btn-ibm p-4 flex flex-col items-start space-y-2 bg-[#161616]">
        <span class="text-[10px] text-[#8d8d8d] font-bold">02</span>
        <span class="text-sm font-semibold uppercase">Cấu hình</span>
    </button>
    <button class="btn-ibm p-4 flex flex-col items-start space-y-2 bg-[#161616]">
        <span class="text-[10px] text-[#8d8d8d] font-bold">03</span>
        <span class="text-sm font-semibold uppercase">API Kết nối</span>
    </button>
    <button class="btn-ibm p-4 flex flex-col items-start space-y-2 bg-[#161616]">
        <span class="text-[10px] text-[#8d8d8d] font-bold">04</span>
        <span class="text-sm font-semibold uppercase">Cộng đồng</span>
    </button>
</nav>

<!-- Execution Input (Giả lập thực thi lệnh) -->
<section class="mt-6">
    <div class="relative">
        <span class="absolute left-3 top-3 text-[#0f62fe]">$</span>
        <input type="text" 
               class="w-full bg-[#161616] border border-[#393939] p-3 pl-8 text-sm focus:outline-none focus:border-[#0f62fe] placeholder-[#525252]"
               placeholder="Nhập lệnh thực thi (e.g. --sync)">
    </div>
</section>

<!-- Footer Stats -->
<footer class="mt-8 grid grid-cols-3 gap-1 border-t border-[#393939] pt-4">
    <div class="text-center border-r border-[#393939]">
        <p class="text-[8px] text-[#8d8d8d] uppercase italic">Memory</p>
        <p class="text-xs font-bold">128MB</p>
    </div>
    <div class="text-center border-r border-[#393939]">
        <p class="text-[8px] text-[#8d8d8d] uppercase italic">Uptime</p>
        <p class="text-xs font-bold">99.9%</p>
    </div>
    <div class="text-center">
        <p class="text-[8px] text-[#8d8d8d] uppercase italic">Region</p>
        <p class="text-xs font-bold">VN-S1</p>
    </div>
</footer>