<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>eloisius</author><text>I’d settle for them making PRs as useful as they were in 2015, before they messed up some of the most basic functionality: showing the diff, and showing review comments. They hide big diffs behind a “load more” link, and as a result people often fail to code review the most substantial part of a change because they scan right past it, thinking it’s a removed file or binary or something. Then, once you submit a review, they only show 10 comments. In the middle, there’s an easy-to-miss “load more comments” button.&lt;p&gt;These are the two most fundamental features of a PR. How could they decide so few as 10 is the right number of comments?</text><parent_chain></parent_chain></comment><story><title>Pull Request File Tree Feedback</title><url>https://github.com/github/feedback/discussions/12341</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>ydnaclementine</author><text>Not sure if this is well known, but press period `.` when viewing a PR, repo, or file and github will send you to a in-browser visual code editor. Able to make commits in there too, perfect for [nit] comments</text><parent_chain></parent_chain></comment><story><title>Pull Request File Tree Feedback</title><url>https://github.com/github/feedback/discussions/12341</url></story>