GitHub Community
New commit details page (public beta) feedback #139005
Replies: 298 comments 393 replies
-
|
My first reaction to the new page was: What is happening now!?! My second impression was: why is everything 50% bigger, did I Ctrl+Scroll to zoom by accident? And my third was: where are the diff count squares? Also I just found the first bug: when having text selected and trying to extend that selection with shift, that no longer works. Also I was just searching a bit for a commit message because since it is now completely grey, I kinda missed it. |
Beta Was this translation helpful? Give feedback.
-
|
@cklam12345 I think you replied to the wrong thread |
Beta Was this translation helpful? Give feedback.
-
|
I wouldn't know where to put a request, so forgive me. |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
If your Grindr account gets banned because of Grindr Plus. Download deviceid changer by silverlabs on Play store. Use deviceid changer select Grindr from the list and click the orange pill button on the right and restart phone. Your account will be unbanned. If you uninstall and reinstall Grindr your account will show as banned you must use deviceid changer after every install/reinstall. |
Beta Was this translation helpful? Give feedback.
-
|
nice |
Beta Was this translation helpful? Give feedback.
-
|
I personally dislike the new page's design. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the feedback here. We are working on a new user setting that will let you control how compact (or not) the spacing is. Look for Compact line height user setting in the discussion description above for our current thinking, background, etc, and let us know what you think! |
Beta Was this translation helpful? Give feedback.
-
|
+1 for customizability in line-spacing. The current default is very weird - I had to double check if there wasn't a stray newline in my generated JSON files. |
Beta Was this translation helpful? Give feedback.
-
I assume you're joking about the appearance of a stray newline (😄), but if you're not ... The current line height is 24px and the font-size is 12px, which means there should be 2-3px above and below the text on each line (so 4-6px between each line, or about 1/4 or 1/3 of the text height). If you're seeing something more than this, please send a screen shot. |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
چه چیزروادغام وتقسیم می کنیدکه کنم بادوتافرمو ل. وحساب کتاب خودتون میدونیدچکارکنیدباکاربران |
Beta Was this translation helpful? Give feedback.
-
|
I cant see now how my files have been changed by size, thats not good |
Beta Was this translation helpful? Give feedback.
-
|
We shipped a fix last night to bring back the diff stat visuals (and also show the +/- numbers). Let us know what you think!
(see the Recent fixes and enhancements ✅ section in the discussion description for this and other recent fixes) |
Beta Was this translation helpful? Give feedback.
-
Thanks for responding to feedback and taking it seriously :) |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
من یکسال وقت وزمان وهزینه اینترانت ندادم که امروزتقسیم بشه ویاباچهارتا فرمول سرکیسه ببندین |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
Thanks for the feedback. We are tracking this, and I've listed it in the description under Known Issues. |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
@generalmimon wrote:
I mostly work alone, and this form factor is good for comments that I wouldn't want in the code itself if they're too messy, but belong to specific lines of code and thus would not go well in the commit message. Think of them like sticky notes on a printout of the code, that I could take to a meeting with other developers, and move onto the whiteboard if helpful. |
Beta Was this translation helpful? Give feedback.
-
Please add this. I've just seen the new UI and had to disable it because reviewing a large file when all comments are hidden was a pain. In the end, I had to go through each one of them to check if I had missed any. |
Beta Was this translation helpful? Give feedback.
-
|
My feedback is, thank you for putting the green "beta" mark with a link to this post explaining. I like the new design, but when it happened, I was in the middle of writing comments on a commit and it was very confusing to me why the design changed. I thought for a little while that the project maintainer was collapsing my comments until I found the link to this page. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for this feedback! This new page will be fully rolled out (in beta) by today, but we have other beta features that will be shipping soon, and we'll make sure to test this flow to ensure nothing breaks (and the experience is not confusing). |
Beta Was this translation helpful? Give feedback.
-
|
That's odd, because my page says "Alpha". I would argue that its live, and there is no way to toggle the page back then you can't really call it a beta. |
Beta Was this translation helpful? Give feedback.
-
|
The problem (as mentioned by others), isn't the scaling, the scaling is actually the same as before. The issue is the If this is for accessibility purposes, then it should be it's own feature preview or option that the user can toggle. Another issue that's not mentioned yet is that commits with really long descriptions now have a "Show more" button instead of just showing the full description. If I'm clicking on a commit, I probably want to read the description. Please don't make me click multiple times. The text could also be made brighter and easier to read as it was before. See with this example commit: mpv-player/mpv@d2f3b66 |
Beta Was this translation helpful? Give feedback.
-
We rolled out a fix for this 🎉. See "Recent fixes and enhancements ✅" above. |
Beta Was this translation helpful? Give feedback.
-
We also just rolled out a new setting that lets you control line height (see description). |
Beta Was this translation helpful? Give feedback.
-
|
I dislike that the file name and path gets shortened despite there being plenty of horizontal space in the bar. And I can't even hover it to get the full path, I have to hover the "expand" button for the purpose of this screenshot. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the feedback. Agree --- there's no reason to truncate the file path when there's plenty of space to show it. I opened an issue. |
Beta Was this translation helpful? Give feedback.
-
|
A fix rolled out for this last night! 🎉 Take a look and let us know if you're still seeing a problem. |
Beta Was this translation helpful? Give feedback.
-
|
Honestly, I liked the old design better. I hope there will be an option to switch between them. |
Beta Was this translation helpful? Give feedback.
-
|
I personally agree with @R0rt1z2, I like that github now finally seems to fit the code view to the full width of the screen (which it previously did not do on 4K displays) but the function call navigation and file navigation sidebars are annoying. I understand the usage of the sidebar navigation but I wish that explicitly dismissing it would keep it hidden and not reopen it when I click, highlight, or navigate in the code. Much like @R0rt1z2, this is mostly personal preference, some of which I fixed with greasemonkey scripts but I still feel the behavior is incorrect. I also agree with the comment box width problem. For a long time, GitHub had used explicit pixel widths for many elements instead of using relative spacing and this made viewing on 4K or higher resolution displays quite annoying. |
Beta Was this translation helpful? Give feedback.
-
Thanks for the feedback. We're looking into it. |
Beta Was this translation helpful? Give feedback.
-
@R0rt1z2 - we rolled out a fix for indentation issues on some browsers. Can you see if it resolves your issue with viewing this commit? |
Beta Was this translation helpful? Give feedback.
-
@willsmythe It seems to be working fine now. I tried with that commit, and the indentation looks correct. I'm using Firefox on Windows.
|
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
... I can't right click to copy/paste the code? |
Beta Was this translation helpful? Give feedback.
-
Noticed this too; selection should (also) stay. |
Beta Was this translation helpful? Give feedback.
-
How about just not hijacking the native right-click behavior? |
Beta Was this translation helpful? Give feedback.
-
|
Try? |
Beta Was this translation helpful? Give feedback.
-
|
This public discutions can i commented too? |
Beta Was this translation helpful? Give feedback.
-
|
بنده روببخشیدعذرمیخوام ولی خداوکیلی ازی طرف ازتحتساب بازیهامون کم میشه ازی طرف اینجاتقسبم حذف میشه |
Beta Was this translation helpful? Give feedback.
-
|
The new design seems to struggle with tab indentation in files. For the sake of completeness I'll mention that the below screenshots are using 4-space tabs in my user settings but the effect in the new design is the same with the default of 8. Old: New: |
Beta Was this translation helpful? Give feedback.
-
|
seems like it's just "swallowing" the first tab, and even more because the first letter is cut off
|
Beta Was this translation helpful? Give feedback.
-
|
I saw just the new commit page for the first time today and it's not understandable to me how Github has not stopped the beta rollout when there's such an obvious bug. |
Beta Was this translation helpful? Give feedback.
-
|
What browser/OS are you all on, and do you have any plugins for GitHub installed? |
Beta Was this translation helpful? Give feedback.
-
|
Firefox on Linux (X11). No plugins or CSS modifications for GH. |
Beta Was this translation helpful? Give feedback.
-
|
The default-collapsed commit text seems to utterly miss the point of the commit details page. It's also much harder to read – the previous page used #1f2328 on #f1f8ff, which has an excellent contrast of Lc 98.0, but the new page uses #59636e on #fff which works out to only Lc 80.5, which is well below the preliminary APCA Bronze threshold of Lc 90. In conjunction with the smaller font size (was 13px, now 12px), the commit text is now very difficult for me to read. Duplicating the first line of the commit text (once in the big heading, once in the monospace body) seems a bit odd:
Lastly, the line-height of the code is uncomfortably large, I really hope you don't intend to use this style across the whole website going forwards. |
Beta Was this translation helpful? Give feedback.
-
|
Ugh, thanks for pointing out the contrast change. Haven't we learned that light-gray-text-on-white is an anti-pattern by now? |
Beta Was this translation helpful? Give feedback.
-
|
I agree, the commit message is much harder to read because of the light gray and shouldn't be collapsed. I don't understand why it feels like there's an aim to de-emphasize the commit message, it's often more important than the code itself! |
Beta Was this translation helpful? Give feedback.
-
|
A fix for the text color problem has rolled out. You should also now see the full commit message. 🎉 |
Beta Was this translation helpful? Give feedback.
-
|
Great |
Beta Was this translation helpful? Give feedback.
-
|
When you start writing a comment, the textbox now expands off-screen:
so you have to scroll down again to see the button to submit the comment now. If the comment box were not collapsed by default, this would be solved. The page also doesn't seem to have the standard GitHub footer, which doesn't help. On wide screens (and by "wide" I mean "16:9 1440p"), having to mouse all the way over to the right-hand side to add a comment makes it really hard to see which line you're commenting on (unless you want to open the dialog, check the line number on the right (which says "R" for some reason?), pull your eyes back to the left-hand side to check the line number there, and try again if you aimed wrong):
And the tooltips on the comment widget buttons ("Heading", "Bold", etc.) appear to have been dropped, which sucks. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for reporting. The team is working on a fix. |
Beta Was this translation helpful? Give feedback.
-
|
Clicking on the line number first boxes that line, and makes it easier to aim when going to the opposite side of the diff listing. |
Beta Was this translation helpful? Give feedback.
-
|
Links to diffs for specific ranges no longer work. The page does not correctly focus the view on the range present in the URL (for example, the URL ending with |
Beta Was this translation helpful? Give feedback.
-
|
I am a heavy mobile user and I need to review code on the go... 
There is so much wasted horizontal space and the wrapping makes things even worse. This makes reading code unbearable... I'd almost say impossible. I've been using a userscript before the new design that made a few css adjustments but seeing that this isn't possible anymore makes this even more frustrating. |
Beta Was this translation helpful? Give feedback.
-
|
One solution for this is to just stop wrapping things. It makes stuff so harder to read on width constrained devices. Or at least let the user toggle the wrapping behavior. |
Beta Was this translation helpful? Give feedback.
-
|
Also the spacing/heights of the file header is just way too big. Again, on mobile this is way worse than desktop. |
Beta Was this translation helpful? Give feedback.
-
Thanks for the feedback. We are exploring adding a user setting, similar to the "wrap lines" setting we have when viewing a file. |
Beta Was this translation helpful? Give feedback.
-
|
Probably you'll have to reconfig your base font-size to more sensible one: Or just need a wardrobe sized screen: |
Beta Was this translation helpful? Give feedback.
-
|
Wi are getting FUKED |
Beta Was this translation helpful? Give feedback.
-
|
Some code can be borderline unreadable on mobile |
Beta Was this translation helpful? Give feedback.
-
|
I just permanently enabled Desktop Mode on my mobile for GitHub links, because the mobile site was already unbearable. Both old and new. |
Beta Was this translation helpful? Give feedback.
-
|
I'm seeing this kind of output even on the desktop. Would prefer to keep things as they were. |
Beta Was this translation helpful? Give feedback.
-
|
Same, this happens on desktop too. I should be able to scroll to see the whole line. Line wrap is not useful here. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the feedback. We are working on a fix for tab/indent behavior, and also exploring adding a user setting to toggle line wrapping. |
Beta Was this translation helpful? Give feedback.
-
|
This should be resolved - are you all still seeing the problem? |
Beta Was this translation helpful? Give feedback.
This comment was marked as spam.
This comment was marked as spam.
-
|
Why aren't my commit reports rendering their markdown?
|
Beta Was this translation helpful? Give feedback.
-
|
Per tradition, it's assumed Plain Text: |
Beta Was this translation helpful? Give feedback.
-
|
Sub-module differences seem to be working again in the new page. Thanks very much for implementing this! 👍 |
Beta Was this translation helpful? Give feedback.
-
|
I still see only the different hashes: How to see the differences inside the submodule? |
Beta Was this translation helpful? Give feedback.
-
|
thats the entire point.. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry, my bad, sub-module differences do not in fact appear to be implemented in a useful form in the new page. This is very disappointing. |
Beta Was this translation helpful? Give feedback.
-
|
LGTM. Submodules are displayed as internally git stored; as just a hash with no redundancy or cross contaminating duplication.
Wouldn't mind the TL;DR; - Rather than showing an invalid recursion like The idea is to be able to drill-down into submodules recursively while remaining precise as to what |
Beta Was this translation helpful? Give feedback.
-
|
I'd just about accepted that display of sub module differences may not make it into the new commit details page as it was "not a priority" but what I hadn't anticipated is there is a school of thought that sees the new spartan, hash difference only display is an improvement and "the entire point". That's something I have to disagree with. Recapping, when a commit contains a change to the linked hash of a sub-module it currently displays a summary of the files affected in the submodule rather than the hash change.
An example, this commit This is not "redundancy or cross contaminating duplication" as it is not stored anywhere but useful reflection of changes in the submodule that feed into the "super module" commit when it is recursed. Clicking on any part of the summary takes you to a commit compare page showing all differences between the two hashes in the sub module. This is not a link to a specific commit on the submodule but link to accumulated changes in commits between the two different hashes on the sub module. @willsmythe, If we're not to have the summary view any more for sub-module updates as it is viewed as clutter, can we at least have a link to the associated "commit compare page" next to the differences in hashes which would be a compromise position (perhaps under the "View File" popdown which is currently "unavailable"). It is very useful having a fast way to review changes implied from a submodule update in any commit and something GitHub currently gets right compared to other git tooling. |
Beta Was this translation helpful? Give feedback.
-
|
regarding relative dates, obviously github users are mostly programmers, it's not the average social network crowd. Obviously they expect detail and punctuality. |
Beta Was this translation helpful? Give feedback.
-
|
Personally I prefer absolute dates in all prose contexts, but certainly for this, relative dates are completely useless. |
Beta Was this translation helpful? Give feedback.
-
|
at a minimum there needs to be a way to see the exact date in a tooltip or something. |
Beta Was this translation helpful? Give feedback.
-
|
Tooltips are problematic for multiple reasons:
|
Beta Was this translation helpful? Give feedback.
-
|
The new page is incorrectly reporting a binary diff as
However, viewing the file directly shows 48.5 KB. Also, the binary file has two "..." menus with identical options. |
Beta Was this translation helpful? Give feedback.
-
|
In commit details it would be very useful (actually essential) to see a more specific commit time than "authored yesterday" for debugging purposes |
Beta Was this translation helpful? Give feedback.
-
|
In a very frequent worst-case we'd see: all dates of relevant comments/commits entirely "last week" alike... Though non-specific to Commits, but the same issue has been brought up literally: @willsmythe, I worked out a probable fix: |
Beta Was this translation helpful? Give feedback.
-
|
Commit updating submodules used to be a link to commit compare page |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as disruptive content.
This comment was marked as disruptive content.
-
|
A date-based commit search/filter would be helpful |
Beta Was this translation helpful? Give feedback.
-
|
Go: https://github.com/orgs/community/discussions/39463#discussioncomment-5111516 |
Beta Was this translation helpful? Give feedback.
-
|
I wish that the floating comments would stand out at least a bit more with a border or a different background: Also, discussing something long within them gets pretty tricky. Because you can't search through them being collapsed. And them being so narrow doesn't help too. |
Beta Was this translation helpful? Give feedback.
-
|
In some cases we don't want floating comments outright: |
Beta Was this translation helpful? Give feedback.
-
|
Name of committer is not shown. (imported after a squash-merge). |
Beta Was this translation helpful? Give feedback.
-
|
title: Connecting to GitHub with SSH
|
Beta Was this translation helpful? Give feedback.
and others
-
A new version of the commit details page is now available in public beta! This new page, which is enabled by default, lets you quickly understand and navigate the changes in a commit with improvements to filtering, commenting, and keyboard navigation!
What's new 🎉
Here are a few of the noteworthy changes:
upanddownkeys on your keyboard. A new context menu also makes it easier to comment, copy, and select.To opt out of the preview, go the Feature Preview dialog on your profile, select New Commit Page, and click Disable.
Let us know what you think!
Investigating 🟨
Things we are discussing and investigating internally (and we welcome your feedback on):
Known issues 🔴
#diff-e727e4R4-R7).) appears before file name in header above diff.gitattributesnot presented as generated)@mention menu does not appear when adding/editing inline commentsIn progress 🧡
(updates coming)
Recent fixes and enhancements ✅
Week of September 16:
Copymenu option not appearing for some users ✅Week of September 23
Screen.Recording.2024-09-26.at.11.34.46.AM.mov
More about compact line height
* Compact line height user setting 🆕: * **What's our plan?** Based on your feedback about the height of diff lines in the new parge, we are adding a user setting under the ⚙️ that you can enable if you want more compact lines. When enabled, the height of diff lines will be `20px` (same as the classic commit details page), otherwise (and by default) they will be `24px`. * **Why a user setting?** It is important that this (and every) page on GitHub is accessible to everyone. [WCAG recommends a minimum of `24x24px` for click targets](https://www.w3.org/WAI/WCAG22/Understanding/target-size-minimum.html) because _some people with physical impairments cannot click small buttons that are close together_. The avatar (which appear when there are comments on a line) and button to add a comment are both important click targets on the line, which is why the default height of the line is 24px. We recognize that some users prefer (and are able to interact with) more compact lines and click targets, which is why we are introducing a user setting.
Beta Was this translation helpful? Give feedback.
All reactions