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
• Code scanning alerts
• 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.

[shekibobo]

Building on this, it would be great to also see outdated comments on a file in a dropdown, so even if they're outdated and don't show up inline in the file diff, they could still be found within the file context.

[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]

[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.

[smil2k]

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?

There are 3-4 chrome extensions to fix this missing feature. Please implement it as it is very annoying to set it each time.

[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.

[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".

[eugenet8k]

What VSCode extension did you use for code review?

[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.

[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.

[otnielyehezkiel]

this happening to me also, stuck loading after filter based on file ownership

[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.

[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.

[JayLathiaTR]

This is an important functionality, where I just ask the Copilot by selecting all files saying - 'What are these changes about and scan for any security flaws for these files'.

So yes, this is required for sure, and this is the only reason - I am not using the new 'File Changed' feature.

[sylv256]

I'd love there to be less shoving AI in everyone's faces and more of this. As soon as I realized the Copilot button wasn't bugging me toward the right of the line of code I hover over, I was happy.

[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.

[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?

[ShaunSHamilton]

I have seen this a few times as well. What I noticed is I would only be show one commit's changes as opposed to "All changes" - even though that option appeared selected.

As other's pointed out, re-selecting the "All changes" fixed the issue.

[willsmythe]

Thanks for the feedback. We're investigating.

[yawkat]

just saw this issue as well.

[chris-martin]

Switching back to the old UI specifically because of this bug.

[romain-trotard]

I have the same problem.
My Step To Reproduce is the following one:

• Click on the View it on Github in the email notification

• And then clicking on the Files changed tab

[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?

[owieth]

I also used to have a nice summary of all changed files for submodules:

OLD:

[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.

[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!

[tanmayairbase]

the new experience doesn't tell whether the CODEOWNERS file is valid or not, unlike the existing/current experience

[Islamsulaiman]

1. In the new experince, I can't hide all the commentsin one section (file diff), mebye I cant find it.
2. Can we still start copilot chat on all files, again I couldn't find it.

[Vahelnir]

The file-per-file review is really helpful ! The only downside is that there's now way to see what files are marked as reviewed and what files aren't at a glance

[ugniusb]

Cannot post a comment while selecting a line range in a file containing more deletions that additions

Failed to save comment: End line parameter is invalid: must be greater than start_line.

The error message is technically correct, of course

[nishutosh-joinventures]

Settings button was on left side earlier. Options like Hide whitespace were easily accessible.

[denishowew]

In Firefox, while editing the text of a comment ("Write" as opposed to "Preview"), command-C doesn't work. It's OK in Chrome.

[MaxByrneFBG]

love

NEW: The file tree is now resizable so you can take advantage of your larger display.

[edwardsph]

There is a lot I like but having comments disappear when you go over the 40 limit makes this a non-starter for me, especially when working with PRs from a junior developer.

[pakohan]

I love the new features that only shows one file, and you can click through them with j / k. I would add two improvements:

• also add a keyboard shortcut to mark a file as viewed
• give me the option to always use the single file view

at least one of the following three features:

• remember the file I left off the last time
• give me the option to only go through the files that are not marked as viewed yet
• mark the viewed files in the tree view

without the last three features the single file view feels like a downgrade, because often I go through bigger PRs, see a mistake, quickly push a fix, and then I have to loop through all the files again if I forgot to remember in which file I was. If I added another file that would be shown as one of the first, then it's hard to find that one with the j key. Sometimes it shows me I didn't mark one file as viewed and I don't know where it is.

[tiagox]

I'm on the other side of the road, please give the ability turn on/off the single file view.

I was trying to disabled it for a 63 files PR, but couldn't.

[n-miles]

Utterly baffling decision to say Due to the large number of changes in this pull request, only one file is being shown at a time.

Who in the world can possibly review a change with a large number of files one file at a time? This is a total dealbreaker.

[heaths]

I've had some where the file count showed the infinity symbol. Those hang the browser. But, still, there should be a higher threshold for "large PR". I often see some with dozens of files that now show me 1 file at a time and, yeah, I agree: that's a dealbreaker.

[Rickmarges]

When a file has been deleted it is not possible to add a comment on the whole file (using the option next to the "viewed" checkbox). This was possible in the previous version:

[jacobeblitz]

The "Comments" dropdown at the top right is not as intuitive as the old view's "Conversations" dropdown that showed you the conversations with resolved pre-filtered out.

[jacobeblitz]

On closer inspection, I'm not even seeing my unresolved comments/conversations in the dropdown menu at all.

[nunoleong]

CTRL+SHIFT+F to toggle the reviewed checkbox on all visible files is a must for me

[nniesen]

The "pull request updated" error state is a little overzealous or doesn't refresh properly. On the "Conversation" tab, I clicked Update the branch, then I switched to the "Files changed" tab, clicked the "Submit review" menu option, marked it "Approved", and click the "Submit review" button at which time I received an error message that the PR was updated. Switching tabs and "reloading" the page by clicking the "Files changed" tab again did not clear the state. I now sometimes you have to click the "Files changed" to "walk-through" the commits since last viewing but this wasn't the case and didn't clear the state. I finally had to force reload the browser window before it let me submit the review. It was a 1 file 2 line change that I could see on the screen so there was nothing more for me to review. I'm not a fan of it blocking a conscious user action. I could see a presenting a warning on the first attempt but after that it should just submit my review.

[danseely]

Another note on the single-file PR diff view: when I select a file in the sidebar, the file is loaded but the page / view is scrolled down instead of re-scrolling back to the top of the page. It seems like it might be trying to match the point I was scrolled to on the previous file? Tough to say for sure given the differing length of diffs, but either way I'd expect the new file to load with the page scrolled to the top.

[zzorba]

There needs to be a way to search all the files for text (among the diff) in a large commit. The old tool lets you do this with the browser, the new one does not.