Finding a file I already know the name of is not a problem. And Ctrl/Cmd+F works just fine for that. What I personally use the file explorer in a PR for is for

Finding a file I already know the name of is not a problem. And Ctrl/Cmd+F works just fine for that. What I personally use the file explorer in a PR for is for various other things. * Quick overview of the "complexity" of the change. If I see a huge list of files or files "all over the place" that let's my spidey senses tingle. Much more so than a simple "X files changed" bit of text could. * Navigating around the changeset by most interesting area first. E.g. I might see at a glance that there are changes in three folders of interest and the rest are less important. I don't read PRs from top to bottom like Github tries to make you. I find that unnatural. * I can also easily, visually, jump around between these areas/files to cross references changes without having to remember their names or scrolling a lot. * In large changes (lots of files in lots of places - it happens sometimes) I can collapse folders that are not interesting or that I'm done with. The fact that I already opened a file once does not tell me anything really as I tend to jump around between files to cross reference things. In fact one great feature to have is to mark a file as "unread" again. Which IIRC Crucible had. YMMV as always and Github does have this as well now, so we're good :)