Improved pull request "Files Changed" experience feedback

[Akash1134]

Important

You can opt in to the public preview from any pull request via ✨Try the new experience in the upper-right corner. You can return to the classic view by clicking the “switch back” link.

About the new experience

This refresh focuses on performance, accessibility, and clarity so reviews stay responsive—even on the largest pull requests.

What’s new ?

Performance 🚀

• Faster diff rendering with significantly lower memory usage.

UX ✨

• NEW: Comment and annotation indicators appear in the file tree to help you quickly identify files with comments, errors, or warnings.
• NEW: Pending comments are shown in the review submission panel so you can look over your comments before submitting.
• NEW: Local draft comments persist across page refreshes.
• NEW: Seamlessly switch between split and unified views.
• NEW: A new side panel helps you discover comments, including the ability to search for text while also providing quick access to errors and warnings (i.e. annotations) reported by status checks.
• NEW: The file tree is now resizable so you can take advantage of your larger display.

Accessibility

• NEW: Consistent keyboard navigation and screen reader landmarks added for better accessibility.
• NEW: Increased line spacing for readability—use Compact line height if you prefer a tighter view

What's missing? 🟨

As of the initial public preview release, there are some temporary limitations that will be addressed over time:

• Applying multiple suggestions at one time (i.e. batching)
• Reviewing a single commit
• Annotations on unchanged files
• Small screen (e.g. mobile device) responsive layout

While our previous experience had hard limits on large PRs, this new experience is being built to scale. That said, we’re increasing our limits incrementally. To start with, our additional current limitations are:

• Limited to 1,000 files
• Comments: 40
• Replies per comment: 20
• Alerts: 50

How you can help

1. Report bugs, edge cases, or usability pain points in the replies (screenshots/gifs welcome).
2. Tell us which future enhancements would make the biggest impact on your workflow.

Thanks for helping us build a better review experience—we read every comment!

[willmarcondeseso]

I would like to be able to scroll through the Pull Request while the comment modal is open.

Reason: When a comment is outdated, we need to look at the current version to check if it actually addresses the comment.

I really love this feature! THANK YOU!!!

[well-known-alex]

So annoying!

[dcumings]

Also the comments disappear from context when changes happen. It would be nice to be able to see them after changes happen. Bitbucket had a great implementation for this

[Bangkah]

yes

[William-Aspen]

Azure DevOps had a strong implementation of this. For reviewers, it’s critical to know whether their comments were applied as intended, and seeing them directly in the updated files makes that process straightforward.

[rtalexk]

Update: I just found out that it appears when there's enough space (1280px width). Here's the updated feedback.

I'd like to see the branch name in the sticky header at all times so that I can easily copy it when I'm reviewing a PR.

---

I wrote the following before thoroughly experimenting.

I'd like to see the branch name when the sticky header is shown (i.e., when you've scrolled to the bottom).

The reason is that when I'm reviewing a long PR and want to checkout the branch to continue reviewing it locally, I have to go back all the way up to see or copy the branch name and then go back to where I left off.

[nniesen]

Similar scrolling issue getting back "Conversation" or "Submit Review" when far down in a large PR. Maybe those could move over into the side navigation or maybe the sticky header briefly becomes a floaty thing when scrolling.

[RentecJeremy]

I came here just to comment "Thank you for the branch name in the sticky header". I can't tell you how many mammoth PR's I've had to scroll up, or duplicate the tab, or (insert method of getting branch name here)... now the branch name is just there and copy-able. 🤌

[albertoblaz]

Similarly, I miss having a sticky bar below the PR's title to have the "Conversation" tab/button visible without having to scroll bar to the top.

Alternatively, users could still do Cmd+Up to scroll up and then click on the tab, but doing so doesn't scroll if the focus is on the diff panel, so you need to click on the files sidebar or the page margins and then use the shortcut.

It's not a critical issue, but a little annoying.

[pakeeza2425]

I know exactly what you mean — the old sticky bar made it so much quicker to jump back to the Conversation tab. Right now the extra scrolling or focus-shifting adds friction, especially during long reviews. A persistent header or sticky navigation with the tabs always visible would be a nice quality-of-life improvement. Not critical, but definitely one of those small things that would make the workflow feel smoother.

[duduedufsa]

This update focuses on three essential pillars of a modern code review experience: performance, UX, and accessibility.

Optimized diff rendering with reduced memory consumption.

[rtalexk]

I find the comment indicators in the sidebar really useful. It might also be useful to have them in the "diff file header."

It's very useful when you've marked a file as "viewed" because you can see how many comments it has as you're scrolling without having to expand it.

[thornevale]

It would be helpful to have a dropdown in the file view that shows outdated comments too. That way, even if they're not shown inline anymore, we can still find and read them in the context of the file.

[maaicondgl]

I agree.

[iifeiss780-wq]

https://github.com/orgs/community/discussions/5486

[dcumings]

[shrynshjn]

this is not showing up for me, rather i am getting a comment option on the pr level, having it on a file level would really be great, current i open two split windows to check my older comments and the latest code.

[rtalexk]

Seamlessly switch between split and unified views.

This is really cool. Is it also possible to seamlessly toggle hiding white spaces? If that's achievable without doing a refresh would be amazing.

[ryansheabla]

Thanks for the feedback.

• We are planning to support seamless switching of "hide whitespace-only changes", but no timeline yet.
• We are also exploring the implications of making this a user-level preference so it would be remembered/applied consistently across all PRs. Do others have thoughts/opinions on this?

Would it be possible to set "Compact line height" as a user preference as well? I like the changes overall but much prefer the original setting.

[jessehersch]

Thanks for the feedback.

• We are planning to support seamless switching of "hide whitespace-only changes", but no timeline yet.
• We are also exploring the implications of making this a user-level preference so it would be remembered/applied consistently across all PRs. Do others have thoughts/opinions on this?

please do this soon. it's been too long! This discussion is 4 years old, and it says the feature was asked for 3 years before that! So long that the original feature request is a dead link. https://github.com/orgs/community/discussions/5486

[Primajin]

It was actually working better in the old flow and there was even a blog post from Github: https://github.blog/changelog/2021-10-14-hiding-whitespace-is-now-remembered-for-each-pull-request/

[pakeeza2425]

The old flow worked better because features like "hide whitespace" were remembered per pull request, as GitHub highlighted in their 2021 blog post
. The new experience seems to have lost some of that convenience, so restoring those capabilities would improve usability.

[mustmodify]

remembering per-user and per-PR seems both obvious and would result in a significantly better experience.

[rtalexk]

Clicking a line number always assumes you want to add a comment.

In the previous experience it only changes the URL to have deep linking.

[aaccioly]

Any workarounds to obtain permanent urls?

[arisacoba]

@rtalexk which browser are you using? Clicking the line number should just highlight the line, not open the add comment flow.

[rtalexk]

I'm using Arc Browser, but this isn't happening anymore. 👀

[thuringia]

This is so much better, I might go back from reviewing with the VSCode extension now 🚀

I love the new alerts panel, unfortunately it looks like pressing a to hide them doesn't work anymore.

Maybe we could have some grouping or clustering in the alerts panel in the future.
For example I would prefer to see alerts raised by the linter first, instead of "this line is not covered by tests".

[JasonZhuWTG]

What VSCode extension did you use for code review?
I think 'GitHub Pull Requests'

[audreyality]

unfortunately it looks like pressing a to hide them doesn't work anymore.

When this feature comes back, it'd be nice if hiding the annotations also stopped them from being added to the clipboard when copying code.

[willsmythe]

Thanks for the feedback. We are planning to restore the ability to use a to hide annotations.

[mccrearyp]

@willsmythe any update on when this is getting added?

[jsync-swirlds]

In addition to using a to hide annotations, can we have a global (user) setting to hide annotations by default?
Having to tap a (which does not always work correctly, particularly for large diffs) for every PR in repos that overuse annotations (a distressingly common practice that makes review a painful chore) is irritating and we're still left with (often) dozens of files that now have no visible change because some irrelevant annotation happened to touch that unchanged file.

[reecefenwick]

I would love to see the file tree sorted alphabetically with folders on top, then files. It is quite jarring to have changed files in the middle of folders when viewing the file tree currently.

Example of current state

App.tsx
components/
hooks/
index.ts
styles/
utils.ts

Example of desired state

components/
hooks/
styles/
App.tsx
index.ts
utils.ts

This would mirror how the majority of developers view the code in their IDE

[reecefenwick]

Files below is preferable IMO for a more consistent experience

But I also would welcome files above, it would be a massive improvement 🙌

[franzliedke]

Indeed, files below would also be consistent with GitHub's own repo tree view.

[warp10]

I see the value in being consistent with the repo’s tree view; nevertheless, having files listed first can have some interesting use cases. For example, if a PR includes a changelog file or a “manifest,” listing files first would make it one of the first (often the very first) files shown, which I think is nice when reviewing code. In my opinion, that would greatly help the review process. Just my two cents.

[parasyte]

I recommend sorting the same way as git diff-tree, which is what I think the old view did.

$ git diff-tree -r ..main
:100644 100644 d68e1befa16c82c562359a15a283a838d72b0727 e24eac8e828629741b34632e9ef2493a9a95d753 M      src/cryptosuite.rs
:000000 100644 0000000000000000000000000000000000000000 9ad4b1337b54bf28686cf4becccac13124fe6747 A      src/cryptosuite/bip340_jcs.rs
:000000 100644 0000000000000000000000000000000000000000 ab474845d58506540e0ac7e6f0e287770efa1b41 A      src/cryptosuite/bip340_rdfc.rs
:000000 100644 0000000000000000000000000000000000000000 92337d2e16e7ec1f1d2ebc0836773c2099538a1d A      src/cryptosuite/transformation.rs
:000000 100644 0000000000000000000000000000000000000000 fa9ba63738d7b46f5f4647deb01328f6b6981777 A      src/cryptosuite/utils.rs
:100644 100644 f016785749ea50aeb255c80d1a08c1f53b108f6e cd40229a1055c0bd102c6f47318b0d874ab83610 M      src/document.rs
:100644 100644 8b798f1b9f21f3699cdd399939664e9ef4744a8d e2de154c3a730a5b055d6e944e0b8adb98e26f57 M      src/update.rs
:100644 100644 8c80fd426222a68987e2938d37549005bc9db2a0 9c98405bb3803c789dd49a23ca291f2fd9b774cd M      src/zcap/proof.rs

Old view:

New view:

[richard-rance]

Most tools put the folders first but I wish the standard was files first.

The files in a folder typically describe its contents. For example READMEs, Changelogs, manifests, public functions/interfaces. The sub folders contain the implementation details. I would like to read those first when reviewing a PR (or writing code).

That lets me see if their description makes sense to someone who does not know the internal implementation details. Then I can drill into the sub folders that contain the described implementation to see if they match.

It also helps for languages, like golang, that have a vendor folder containing a copy of all dependencies. It would end up at the end of the PR which is perfect since I basically ignore it when doing a review. Right now I have to scroll past all the vendor files to get to the top level files. That can lead to them being missed.

[Nilomiranda]

I don't see the option to comment on the file itself, only on specific lines.

Some files just get stuck into a loading state, like this one:

The comments tab is really nice, I like being able to filter comments by author, makes it much easier to navigate the reviews and attend to the requested changes or overall feedback.

[evenkov]

I don't see the option to comment on the file itself, only on specific lines.

Some files just get stuck into a loading state, like this one:

The comments tab is really nice, I like being able to filter comments by author, makes it much easier to navigate the reviews and attend to the requested changes or overall feedback.

I have the same problems with "stuck info" for some of my files.

[Asfand6417]

Ok

[iifeiss780-wq]

App.tsx

components/
hooks/
index.ts
styles/
utils.ts

[ia0-review]

Should there be a separate thread for the "loading state" issue? I'm afraid this might be buried because the "comment on file" issue has been fixed.

[adcoelho]

This is still happening for me when selecting "Files owned by me". They don't load, and I am unable to review. Any known workaround?

[jieyouxu]

Hi, I would like to play around with this, but I'm not seeing the opt-in mentioned in

You can opt in to the public preview from any pull request via “✨Try the new experience” in the upper-right corner. You can return to the classic view by clicking the “switch back” link.

Am I missing something?

[imanmahjoubi]

We are rolling this out to users slowly, you should be able to see it soon 🎉

[margaret-lin]

The tab for Ask Copilot seems to be missing, also when hovering over lines.

[vitorklock]

My team has the process of always asking Copilot "Any mistakes made? Review this PR" before doing manual reviews.
Just like @JayLathiaTR, I think that being able to talk to Copilot about all the changes is an important feature.
This would also be an improvement, because previously I had to manually click all checkboxes, sometimes more than a hundred of them.

[rr-jimmy-multani]

I'd prefer that this button stay since it's related to the PR and its changes.

[daira]

Feature request: allow people who object to AI (and there are many of us) to turn it off, completely, without the risk of accidentally using it by some misclick or dark pattern.

[3nprob]

Bug: This button is visible even if Copilot is fully disabled in user settings.

[Biglulux]

Asking Copilot to summarize the PR is important to my workflow, so I would like the Ask Copilot button to return to the Files Changed page as well. An alternative could be allowing non-main branch files to be attached to regular Copilot chat, since currently only files on the main branch for all repos can be attached.

[njvrzm]

Not sure if this is the sort of feedback you're after, but the :shipit: emoji does not preview in the review textbox in the new version 😅 . It does show up correctly in the preview.

[willsmythe]

Thanks for the feedback. We'll address.

[cmargonis]

On the topic of emojis, I really liked that I could type e.g. :idea and it would suggest the 💡 emoji. It would be great if this functionality were preserved (or even expanded upon 🙏 )

[KeithYeh]

1. I can't find "comment on this file" button in new UI

Old UI

2. How to hide alerts? I can toggle alerts by pressing "A" in old UI

[willsmythe]

Thanks for the feedback. Both are known issues we're tracking.

[airvision-tw]

Indeed! I am also missing this functionality in the new view.

[cristinadoroftei]

True, I use the "comment on this file" feature quite often and I switched to the old view just because it's missing on the new one 😿

[Smolyan91]

+

[julioag-rmd]

On the Files changed tab I can only see 19 files out of 66. Why?

[lucagiovagnoli]

Switched back to the old UI specifically because of the "Files changed" bug. It's pretty risky to review thinking it's all changes, but really it's only one commit.

[justingrant]

Confirmed that this bug still exists. Here's a more comprehensive repro, and showing the workaround which is to filter to a different commit, then to reset the filter to show all commits.

1. Click "View it on GitHub" link from email notification
2. Click on "Files Changed (11)" tab

Expected: see changes for all 11 files
Actual: only shows changes from one file, even though the commit filter claims to be showing all commits.

3. Click on Commits tab again
4. Click back to Files Changed (11) tab

Expected: see changes for all 11 files
Actual: No change from above: only shows changes from that commit

5. Click on Commits tab again
6. Filter to only one commit
7. Now reset commit filter to show all commits
8. Click back to Files Changed (11) tab
9. Finally, it works normally! All commits' changes are shown.

[justingrant]

@willsmythe Given the severity of the issue and the fact that that it's been present for at least 3 months already, I assume that fixing this (or finding a repro?) is hard. Do you need any more info to repro and fix this? I can repro it easily.

As mentioned by others above, this bug kinda makes the new UI dangerous to use so I'm gonna have to turn it off soon, which is a bummer. Please let us know when this issue is fixed so we can all turn the new UI back on. Thanks.

[anna-intellegens]

This has been driving me crazy. It happens every time I follow a link from an email, which for me means almost every time I go to review something I now have to remember that the UI is lying to me, which is infuriating!

[mdfox20]

Also switched back to the old UI because of this! I almost always open PRs from the email link, so this is a completely breaking bug for me.

[vengut]

I used to be able to click on a useful link to see the submodule diff in PRs but now its just plain text.
Old:

New:

Could we have that back pls?

[cdunford]

👍 any of the above; missing being able to see what changed; I have to flip back to do the old experience to do it

[Lachy-Antero]

Our release process heavily relies on the ability to click through to see the commit diff of submodules. Will be very sad to see this go.

[hsl0]

I want to see that nice summary of changes for non-GitHub hosted submodules, too.

[jlc6]

I would like to be able to see which commit I’m starting from and which one I’m going to in the changed submodules, as the old interface used to show.

[AminHeidaridahoee]

I also want to see the submodule commitId change in the file preview, it is necessary for our code review

[BE-Code]

It doesn't always seem to remember if hide whitespace was turned on.

[Scramle]

Currently, I think the toggle is just backwards. "Hide whitespace" turned on sets the query param to ?w=1, and turning it of sets it to ?w=0. Expected behaviour should be the other way around. So in @rmartins0's case, that link works as it should, as w=1 shows whitespaces and w=0 hides them.

[shahmir-oscilar]

I believe i was able to reproduce this. See steps at: https://github.com/orgs/community/discussions/163932#discussioncomment-13915305

[FeBe95]

Related: https://github.com/orgs/community/discussions/163932#discussioncomment-14012281

[warwick-kiwibank]

A certain order of the URL parameters triggers this bug. This works:
.../files?w=1&file-filters%5B%5D=.yml&file-filters%5B%5D=.tf

But if I put the hide-whitespace parameter after the file-filter parameters, it doesn't work:
.../files?file-filters%5B%5D=.yml&file-filters%5B%5D=.tf&w=1

The parameters are added to the URL in the order of selecting the options in the GUI. So, to avoid the bug, you need to show/hide whitespace, then apply file filters.

The old UI works as expected.

[Bangkah]

Same issue here on Win 11 + Edge 124. Worked after disabling “XYZ” flag. Thanks for the workaround!

[tjwelde]

Would be nice to have an indicator in the file-tree, if a file was viewed or not. (The checkbox in the filter already helps)
Maybe make it bold, if unviewed, or an icon next to it?

Otherwise I love it

[imanmahjoubi]

@tjwelde that's a great idea. Thank you for sharing your feedback

[gajop-ptx]

I am sure this was mentioned before, but I don't see it at the top:

Going through large PRs with 100s of files, one file at a time is insanely inefficient and the main reason I switch back to the "classic" mode. If this becomes the new default I probably won't use GitHub to do such reviews and will review it locally rather.

I understand the desire to reduce browser strain, but can't you do it in batches of 20, 50, 100? One at a time is not an option.

[foges]

Agreed. It might work if it was super quick to hop through files, but the way it currently works it's not really usable

[imanmahjoubi]

@gajop-ptx Thank you for sharing your feedback, have you tried Copilot groups on that PR? it's a new feature that was designed to help with these kind of PRs? can you also elaborate on what exactly is not working?

[tarajeanne]

When changing a file name, I cannot see the old file name in the new UI, which makes it difficult to properly review the changes.

Old UI

New UI

[imanmahjoubi]

Thank you for your feedback! I'm forwarding this to the team

[solak]

When viewing a pull request with many changed files, I can only see one file at a time. This is not helpful and feels like a downgrade compared to the previous UI, which displayed all files together with long ones truncated.

[kandji-joe]

As i'm 'j' and 'k' ing through files on a larger PR, it'd be nice if the file tree (in the sidebar) scrolled automatically so I can see in the tree the active file I'm viewing.

[straversi]

To view changes since my last review, I now have to click "Files changed" tab > "All commits" button > "Changes since your last review", when before I could just click "Changes since your last review" straight from the main "Conversation" tab on a PR. This common flow (for me) is harder now.

[nathanboktae]

The single file at a time in PRs with a large amount of files is a terrible idea. I'm on a platform team that does large refactors with repeated changes and being able to quickly scan files is very important. this change would render the PR review UI beyond unusable if I had to click every single file.

[bradlitterell]

I think it's highly context dependent. When the files have only a few lines changed, but a larger PR where the changes to some files may be extensive, I find the single file view better.

So, I think the upshot of all this is - let the user decide how they want to see it - instead of having github decide for the user.

[bradlitterell]

... And while we are on the topic, let the user decide how much context they want to see when showing the abbreviated view.

[crockerderek92-cloud]

brad i agree

…

On Thu, Nov 6, 2025, 1:43 PM Brad Litterell ***@***.***> wrote: I think it's highly context dependent. When the files have only a few lines changed, but a larger PR where the changes to some files may be extensive, I find the single file view better. So, I think the upshot of all this is - let the user decide how they want to see it - instead of having github decide for the user. — Reply to this email directly, view it on GitHub <#163932 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BZTW2Y3C4IIMSOXGJUFOACD33OJGHAVCNFSM6AAAAACAABXI52VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIOBZGQ3TQNA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.*** com>

[erikbjoern]

Something is broken with the modal for selecting "specific commits":

• If I'm at the top of the page when I click "All commits" -> "Specific commit..." the modal shows as expected, but if I scroll down the modal and overlay disappears, but nothing is interactive. It appears again if I scroll up.
• If I'm not at the top of the page when I click "All commits" -> "Specific commit...", the page auto-scrolls to the top but the modal and overlay is invisible. If I scroll down a little, it appears, but disappears again if I scroll too far down.

(Tested on Google Chrome / Mac OS)

[talldan]

(Tested on Brave / Mac OS) The floating + button for adding comments can be quite hard to click, especially if you have a multiple lines currently selected (the video is a little bit deliberate, but shows what I mean, the + completely disappears even when hovering right where it should be):

Kapture.2025-11-07.at.16.24.37.mp4

It looks like the line number or code row is focusable and intercepts the focus.

From a usability point of view, I don't think I would ever select a range of lines and then leave a comment in the middle of the selection, perhaps the button should be anchored and always appear on the last selected line whenever multiple lines are selected.

[jdelStrother]

It seems unusable on larger pull requests. I'm currently looking at a linting change that touched 2000 lines across 439 files, and it just causes Safari to consume 170% CPU and become unresponsive for minutes on end.

[hfcpeixoto]

While hovering in the file name, the multiple icons are spawned and remain on screen. They have no tooltip to keep tabs on what they are supposed to mean.

It only happens in the first file of the "Files changed" tab.

[djrenren]

It's very difficult to see unresolved comments. I wanted to go through and add a bunch of suggested changes to a batch but there was little if any visual distinction between resolved and unresolved comments and they were hard to locate in the first place.

[cmenjivar]

Can we please get the "Viewed" checkboxes on the PR File Tree, it would be much easier to visualize files/folders already reviewed

[coryrc]

Click the comment button just to left of "Submit Review" button. It has a 5 on it.

There are three threads; I'm pretty sure all 3 are already resolved. Press the "Resolve Conversation" button: "Failed to resolve thread".

https://github.com/openscad/openscad/pull/6251/files#r2425051653