New commit details page (public beta) feedback

[willsmythe]

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:

• Floating comments: Code comments float over the diff when selected. To select, click on the commenter's avatar to the right of the line.
• Comment counts: To help you identify files with comments, the number of comments for a file now appears in the file tree.
• Keyboard navigation within diffs: You can now navigate around changed lines in the diff using the up and down keys on your keyboard. A new context menu also makes it easier to comment, copy, and select.
• Quick view switching: Switching between unified and split views no longer reloads the page.
• Filter by file extension: Easily filter changed files by file extension in the diff to see the content most relevant to you.
• Filtered out diffs hidden: When filtering the file tree, diffs are filtered as well, allowing you to reduce distraction and see the files you care about most.

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):

• Showing all code comments at the same time (like how the original page works)
• User setting to wrap lines

Known issues 🔴

• Floating comment dialog appears outside the viewport (or causes the page to scroll when it appears)
• Page sometimes scrolls when a diff line is selected
• Page scrolls when "add a comment" dialog is opened
• Lines are not selected when link contains a range (e.g. #diff-e727e4R4-R7)
• File extension (or just .) appears before file name in header above diff
• Generated files (identified in .gitattributes not presented as generated)
• Ordering of files in the tree doesn't always match ordering of diffs
• Diff context text (e.g. function names) cannot be selected/copied
• Unable to click drag multiple diff lines (to select a range)
• Fixed-width (monospace) font user preference not honored in commenting forms
• @ mention menu does not appear when adding/editing inline comments

In progress 🧡

(updates coming)

Recent fixes and enhancements ✅

Week of September 16:

• FIXED: Full commit message not shown (hidden behind "Show More") ✅
• FIXED: Commit message text color is too light ✅
• FIXED: Diff stat visuals (green/red +/- boxes) missing in the header of each file ✅
  
• FIXED: File path above each diff was unnecessarily truncated ✅
• FIXED: Copy menu option not appearing for some users ✅

Week of September 23

• FIXED: The native browser context menu now appears when right-clicking diff lines. To access our custom menu (which now groups actions together) use the drop-down on the action bar at the right of the line.
• FIXED: When no files match the filter conditions, a message now appears (previously nothing was shown)
• FIXED: Tab indents not rendering correctly on some browsers (we also switched back to not identing wrapped lines; previously we tried to maintain the first line's indentation level, and will continue to explore this)
• NEW: A new user preference Compact line height lets you opt into a more compact line height. You can toggle it from the view settings (⚙️) menu near the top of the page.

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.

[SuperSandro2000]

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?
Edit: Actually it looks a lot more like the old one when going to 90% zoom 😂

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.

[Roy228]

nice

[Saleh5515]

@cklam12345 I think you replied to the wrong thread

[Nguyen-toan891]

###that la ok

[polybiusproxy]

I personally dislike the new page's design.
As someone who likes to have things small, I browse and use GitHub at 90% zoom on my browser, and I believe this new design makes things bigger than they should, and the increase of the line height looks unappealing to my eyes.

[willsmythe]

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!

[captn3m0]

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

[willsmythe]

The current default is very weird - I had to double check if there wasn't a stray newline in my generated JSON files

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.

[homira135]

چه چیزروادغام وتقسیم می کنیدکه کنم بادوتافرمو ل. وحساب کتاب خودتون میدونیدچکارکنیدباکاربران

[pckotzer]

I cant see now how my files have been changed by size, thats not good

[willsmythe]

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)

[dylmye]

We shipped a fix last night to bring back the diff stat visuals (and also show the +/- numbers). Let us know what you think!

Thanks for responding to feedback and taking it seriously :)

[homira135]

من یکسال وقت وزمان وهزینه اینترانت ندادم که امروزتقسیم بشه ویاباچهارتا فرمول سرکیسه ببندین

[JayDi85]

1. Comment marks near file are good
2. Collapsed comments for better code review are good
3. Need additional features like: fast show/collapse all comments -- e.g. two working modes: first use for code review without comments (collapsed) and second+ uses for discussions with fully visible comments

[willsmythe]

Also, if I try editing the floating comment, I can see that it doesn't respect my setting of Use a fixed-width (monospace) font when editing Markdown

Thanks for the feedback. We are tracking this, and I've listed it in the description under Known Issues.

[adlai]

@generalmimon wrote:

[...] floating comments - they seem to have been designed with very short comments in mind (e.g. one sentence)

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.

[junior-santana]

Thanks for the feedback, @JayDi85 !

Need additional features like: fast show/collapse all comments -- e.g. two working modes: first use for code review without comments (collapsed) and second+ uses for discussions with fully visible comments

This is something we are exploring. We would probably offer the option to show comments "floating" (like this new page) or "inline" (like the current page). Would this work?

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.
Also, the comment button is very subtle, especially in the new design, and it's a bit buggy (sometimes it just doesn't open and the page scrolls to random places)

[robertkirkman]

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.

[willsmythe]

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

[CY2-DavidW]

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.

[llyyr]

The problem (as mentioned by others), isn't the scaling, the scaling is actually the same as before.

The issue is the height and line-height set for .diff-line-row. Just let my browser figure out what the line height should be instead of hardcoding some line height.

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

[willsmythe]

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

We rolled out a fix for this 🎉. See "Recent fixes and enhancements ✅" above.

[willsmythe]

The issue is the height and line-height set for .diff-line-row

We also just rolled out a new setting that lets you control line height (see description). Compact line height avoids adding any extra padding.

[Bilka2]

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.

[willsmythe]

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.

[willsmythe]

A fix rolled out for this last night! 🎉 Take a look and let us know if you're still seeing a problem.

[R0rt1z2]

Honestly, I liked the old design better. I hope there will be an option to switch between them.

[Justasic]

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.

[willsmythe]

Another (very) annoying issue I’ve noticed is that the indentation appears to be broken in some cases. See this commit for example.

Thanks for the feedback. We're looking into it.

[willsmythe]

Another (very) annoying issue I’ve noticed is that the indentation appears to be broken in some cases. See this commit for example.

@R0rt1z2 - we rolled out a fix for indentation issues on some browsers. Can you see if it resolves your issue with viewing this commit?

[R0rt1z2]

@R0rt1z2 - we rolled out a fix for indentation issues on some browsers. Can you see if it resolves your issue with viewing this commit?

@willsmythe It seems to be working fine now. I tried with that commit, and the indentation looks correct. I'm using Firefox on Windows.

[jrbyrnes]

... I can't right click to copy/paste the code?

[mfn]

aha – I guess then it doesn't work because, when I right-click, my selection is cleared.

Noticed this too; selection should (also) stay.

[smuuf]

When it works, it should copy any currently selected text (if any) otherwise it will copy the selected line.

How about just not hijacking the native right-click behavior?

[MasterInQuestion]

    Try?
    https://github.com/orgs/community/discussions/139005#discussioncomment-10715574

[Metanesia]

This public discutions can i commented too?

[homira135]

بنده روببخشیدعذرمیخوام ولی خداوکیلی ازی طرف ازتحتساب بازیهامون کم میشه ازی طرف اینجاتقسبم حذف میشه

[ForLoveOfCats]

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:

[yugecin]

seems like it's just "swallowing" the first tab, and even more because the first letter is cut off

old:

[sfan5]

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.
Fortunately I can just opt-out.

[AdamShwert]

What browser/OS are you all on, and do you have any plugins for GitHub installed?

[sfan5]

Firefox on Linux (X11). No plugins or CSS modifications for GH.

[sersorrel]

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.

[alphapapa]

Ugh, thanks for pointing out the contrast change. Haven't we learned that light-gray-text-on-white is an anti-pattern by now?

[legoktm]

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!

[willsmythe]

A fix for the text color problem has rolled out. You should also now see the full commit message. 🎉

[apripista]

Great

[sersorrel]

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.

[willsmythe]

Thanks for reporting. The team is working on a fix.

[adlai]

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.

[adapap]

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 #diff-<sha>R<000>-R<111>.

[cynecx]

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.

[cynecx]

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.

[cynecx]

Also the spacing/heights of the file header is just way too big. Again, on mobile this is way worse than desktop.

[willsmythe]

Or at least let the user toggle the wrapping behavior.

Thanks for the feedback. We are exploring adding a user setting, similar to the "wrap lines" setting we have when viewing a file.

[MasterInQuestion]

    Probably you'll have to reconfig your base font-size to more sensible one:
    Such clipping is regardless unusable.

    Or just need a wardrobe sized screen:
    Mobile immobile... Never mind.

[KNYNE88YAKIMAWA]

Wi are getting FUKED

[ayylmaobackup]

Some code can be borderline unreadable on mobile

[prashbhat]

I'm seeing this kind of output even on the desktop. Would prefer to keep things as they were.

[jakub-cernik]

Same, this happens on desktop too. I should be able to scroll to see the whole line. Line wrap is not useful here.

[willsmythe]

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.

[AdamShwert]

This should be resolved - are you all still seeing the problem?

[Rockyspade]

fixed <tab/indent> beta 3.0 update status

[kasalava]

👍

[Goldendragon1029]

The commit details only show a fraction of the files changed, both in the directory viewer and the diff viewer. Furthermore, the search box does not work reliably. I know for a fact that I changed a specific file in that commit, but it does not appear in either the directory view or the diff view.

[efahl]

Is anyone else seeing this?

As of a 2024-11-29, the "Comments" section of the commit details page will not display. It simply spins with a greyed-out template of a comment and shows Comments 0 above the template. The strange thing is that comments are displayed and rendered properly when I log out, though, as soon as I log in they misbehave.

Here's an example where I see everything but the comments (you can see where I commented directly via web, but then it stopped and I had to respond via email):
openwrt/buildbot@a75ce02

Tried it on Fedora Firefox, Ubuntu Firefox, Win10 Firefox, Chrome, Opera and Edge. Same behavior everywhere.

[MasterInQuestion]

    Refer?
    https://github.com/orgs/community/discussions/140413

    Parent post is:
    https://github.com/orgs/community/discussions/139005#discussioncomment-10713581
    .
    With various piled-up mountain-like complaints.

[efahl]

Yes, that describes it exactly, thanks!

I disabled the "New Commit Details Page" in feature preview and it works again.

[tobico]

There should be a link from the commit details page directly to any Pull Requests which include that commit.

This is something that I do all the time and have to look up online how to do it every time.

[injust]

The buttons to expand a diff upward/downward seem to be broken. It's the ExpandableHunkHeaderDiffLine ones with aria-label=Expand file up/down from line....

[RobertKrawitz]

I'm disappointed that the issue of absolute vs. relative timestamps is not being addressed or even mentioned, despite this being a clear pain point for many as reflected in the comments. Having an option to choose absolute timestamps (vs. "yesterday" or the like) would be of enormous value to many of us, and the revamp of the commit detail page would be an excellent opportunity to make changes.

[wtarreau]

I'm still enormously missing a direct link to the original and patche files, as well as a direct link to download the patch in git-archive format, with ordered numbers (because fiddling with the URL, in addition to being a pain, also produces patches named after their hash, making it hard to re-apply them in order). This is very often needed, every time you have to edit a patch before applying it (to fix typos, add missing tags etc).

[kkrishTa]

My commit has Azure Kubernetes Service abbreviated to AKS. This got autocorrected to ASK (ask) everywhere!

[MasterInQuestion]

    I don't think GitHub has ever such meddled commit content or message.
    Refer: https://github.com/orgs/community/discussions/142407#discussioncomment-11035153
    Though it did meddle commit messages alike:
    https://github.com/orgs/community/discussions/139005#discussioncomment-11058007

    Probably it's some malconfigured spell checker on your side.

[Agtxcjr]

يتوفر الآن إصدار جديد من صفحة تفاصيل الالتزام في النسخة التجريبية العامة! تتيح لك هذه الصفحة الجديدة، التي يتم تمكينها افتراضيًا، فهم التغييرات في الالتزام والتنقل بينها بسرعة مع تحسينات في التصفية والتعليق والتنقل عبر لوحة المفاتيح!

### ما الجديد 🎉 وفيما يلي بعض التغييرات الجديرة بالملاحظة:

• التعليقات العائمة : تطفو تعليقات الكود فوق الاختلاف عند تحديدها. لتحديدها، انقر فوق الصورة الرمزية للمعلق على يمين السطر.
• عدد التعليقات : لمساعدتك في تحديد الملفات التي تحتوي على تعليقات، يظهر الآن عدد التعليقات الخاصة بالملف في شجرة الملفات.
• التنقل عبر لوحة المفاتيح داخل الاختلافات : يمكنك الآن التنقل بين الأسطر المتغيرة في الاختلافات باستخدام مفتاحي upو downعلى لوحة المفاتيح. كما تسهل قائمة السياق الجديدة التعليق والنسخ والتحديد.
• التبديل السريع بين العرضين الموحد والمنقسم: لم يعد التبديل بين العرض الموحد والمنقسم يؤدي إلى إعادة تحميل الصفحة.
• التصفية حسب امتداد الملف : قم بسهولة بتصفية الملفات التي تم تغييرها حسب امتداد الملف في الاختلاف لرؤية المحتوى الأكثر ملاءمة لك.
• تصفية الاختلافات المخفية : عند تصفية شجرة الملفات، تتم تصفية الاختلافات أيضًا، مما يسمح لك بتقليل التشتيت ورؤية الملفات التي تهمك أكثر من غيرها.

لإلغاء الاشتراك في المعاينة، انتقل إلى مربع حوار معاينة الميزة في ملفك الشخصي، وحدد صفحة الالتزام الجديدة ، ثم انقر فوق تعطيل .

أخبرنا ما رأيك!

جاري التحقيق 🟨

الأمور التي نناقشها ونحقق فيها داخليًا (ونرحب بتعليقاتكم عليها):

• عرض جميع تعليقات الكود في نفس الوقت (مثل كيفية عمل الصفحة الأصلية)
• إعداد المستخدم لتغليف الخطوط

المشاكل المعروفة 🔴

• يظهر مربع حوار التعليق العائم خارج نافذة العرض (أو يتسبب في تمرير الصفحة عند ظهوره)
• تنتقل الصفحة أحيانًا عند تحديد سطر مختلف
• تنتقل الصفحة عند فتح مربع الحوار "إضافة تعليق"
• لا يتم تحديد الخطوط عندما يحتوي الرابط على نطاق (على سبيل المثال #diff-e727e4R4-R7)
• يظهر امتداد الملف (أو فقط .) قبل اسم الملف في العنوان أعلى الاختلاف
• الملفات المولدة (التي تم تحديدها .gitattributesولم يتم تقديمها على أنها مولدة)
• ترتيب الملفات في الشجرة لا يتطابق دائمًا مع ترتيب الاختلافات
• لا يمكن تحديد/نسخ نص السياق المختلف (مثل أسماء الوظائف)
• غير قادر على النقر أو السحب لخطوط الاختلاف المتعددة (لتحديد نطاق)
• لا يتم مراعاة تفضيلات المستخدم للخط ذي العرض الثابت (المسافة الواحدة) في نماذج التعليق
• @لا تظهر قائمة "الذكر" عند إضافة/تحرير التعليقات المضمنة

جاري التنفيذ 🧡

(التحديثات قادمة)

الإصلاحات والتحسينات الأخيرة ✅

أسبوع 16 سبتمبر:

• تم الإصلاح : رسالة الالتزام الكامل غير معروضة (مخفية خلف "إظهار المزيد") ✅
• تم الإصلاح : لون نص رسالة الالتزام فاتح للغاية ✅
• تم الإصلاح : صور الإحصائيات المختلفة (مربعات خضراء/حمراء +/-) مفقودة في رأس كل ملف ✅
  
• تم الإصلاح : تم اقتطاع مسار الملف أعلى كل اختلاف بشكل غير ضروري ✅
• تم الإصلاح : Copyخيار القائمة لا يظهر لبعض المستخدمين ✅

اسبوع 23 سبتمبر

• تم الإصلاح : تظهر الآن قائمة سياق المتصفح الأصلية عند النقر بزر الماوس الأيمن على خطوط الاختلاف. للوصول إلى القائمة المخصصة (التي تجمع الإجراءات معًا الآن)، استخدم القائمة المنسدلة في شريط الإجراءات على يمين الخط.
• تم الإصلاح : عندما لا تتطابق أي ملفات مع شروط الفلتر، تظهر رسالة الآن (لم يتم عرض أي شيء سابقًا)
• تم الإصلاح : لم يتم عرض المسافات البادئة لعلامات التبويب بشكل صحيح في بعض المتصفحات (لقد عدنا أيضًا إلى عدم تحديد الخطوط الملتفة؛ في السابق حاولنا الحفاظ على مستوى المسافة البادئة للسطر الأول، وسنستمر في استكشاف هذا)
• جديد : تفضيلات المستخدم الجديدة: يتيح لك ارتفاع الخط المضغوط اختيار ارتفاع خط أكثر إحكامًا. يمكنك تبديله من قائمة إعدادات العرض (⚙️) بالقرب من أعلى الصفحة.

تسجيل الشاشة.2024-09-26.at.11.34.46.AM.mov
المزيد حول ارتفاع الخط المضغوط

[Nguyen-toan891]

Phiên bản mới của trang chi tiết cam kết hiện đã có sẵn trong bản beta công khai! Trang mới này, được bật theo mặc định, cho phép bạn nhanh chóng hiểu và điều hướng các thay đổi trong cam kết với các cải tiến về lọc, nhận xét và điều hướng bàn phím!

### Có gì mới � Dưới đây là một vài thay đổi đáng chú ý:

• Nhận xét nổi: Nhận xét mã nổi trên sự khác biệt khi được chọn. Để chọn, hãy nhấp vào hình đại diện của người bình luận ở bên phải của dòng.
• Số lượng nhận xét: Để giúp bạn xác định các tệp có nhận xét, số lượng nhận xét cho một tệp hiện xuất hiện trong cây tệp.
• Keyboard navigation within diffs: You can now navigate around changed lines in the diff using the up and down keys on your keyboard. A new context menu also makes it easier to comment, copy, and select.
• Chuyển đổi chế độ xem nhanh: Chuyển đổi giữa chế độ xem thống nhất và chia nhỏ không còn tải lại trang nữa.
• Lọc theo phần mở rộng tệp: Dễ dàng lọc các tệp đã thay đổi theo phần mở rộng tệp trong diff để xem nội dung phù hợp nhất với bạn.
• Lọc ra các khác biệt bị ẩn: Khi lọc cây tệp, các khác biệt cũng được lọc, cho phép bạn giảm phân tâm và xem các tệp bạn quan tâm nhất.

Để chọn không tham gia bản xem trước, hãy chuyển đến hộp thoại Xem trước tính năng trên hồ sơ của bạn, chọn **Trang cam kết mới **và nhấp vào Tắt.

Hãy cho chúng tôi biết bạn nghĩ gì!

Điều tra �

Những điều chúng tôi đang thảo luận và điều tra nội bộ (và chúng tôi hoan nghênh phản hồi của bạn):

• Hiển thị tất cả các nhận xét mã cùng một lúc (giống như cách trang gốc hoạt động)
• Cài đặt người dùng để quấn các dòng

Các vấn đề đã biết �

• Hộp thoại nhận xét nổi xuất hiện bên ngoài khung nhìn (hoặc khiến trang cuộn khi nó xuất hiện)
• Trang đôi khi cuộn khi một dòng khác được chọn
• Trang cuộn khi hộp thoại "thêm nhận xét" được mở
• Các dòng không được chọn khi liên kết chứa một phạm vi (ví dụ: #diff-e727e4R4-R7)
• Phần mở rộng tệp (hoặc đơn giản là .) xuất hiện trước tên tệp trong tiêu đề phía trên diff
• Generated files (identified in .gitattributes not presented as generated)
• Thứ tự các tệp trong cây không phải lúc nào cũng khớp với thứ tự của các khác biệt
• Văn bản ngữ cảnh khác nhau (ví dụ: tên hàm) không thể được chọn/sao chép
• Không thể nhấp và kéo nhiều dòng khác nhau (để chọn một phạm vi)
• Tùy chọn người dùng phông chữ có chiều rộng cố định (không gian đơn) không được tôn trọng trong các biểu mẫu nhận xét
• @menu đề cập không xuất hiện khi thêm/chỉnh sửa nhận xét nội tuyến

Đang tiến hành �

(cập nhật sắp tới)

Các bản sửa lỗi và cải tiến gần đây ✅

Tuần của ngày 16 tháng 9:

• ĐÃ CỐ ĐỊNH: Thông báo cam kết đầy đủ không được hiển thị (ẩn đằng sau "Hiển thị thêm") ✅
• ĐÃ SỬA: Màu văn bản tin nhắn cam kết quá nhạt ✅
• ĐÃ CỐ ĐỊNH: Hình ảnh thống kê khác biệt (các hộp màu xanh lá cây/đỏ +/-) bị thiếu trong tiêu đề của mỗi tệp ✅
  
• ĐÃ CỐ ĐỊNH: Đường dẫn tệp phía trên mỗi khác biệt bị cắt ngắn một cách không cần thiết ✅
• FIXED: Copy menu option not appearing for some users ✅

Tuần của ngày 23 tháng 9

• ĐÃ CỐ ĐỊNH: Menu ngữ cảnh của trình duyệt gốc hiện xuất hiện khi nhấp chuột phải vào các dòng khác biệt. Để truy cập menu tùy chỉnh của chúng tôi (hiện nhóm các hành động lại với nhau), hãy sử dụng trình đơn thả xuống trên thanh hành động ở bên phải dòng.
• ĐÃ SỬA: Khi không có tệp nào khớp với điều kiện bộ lọc, một thông báo sẽ xuất hiện (trước đây không có gì được hiển thị)
• ĐÃ CỐ ĐỊNH: Các thụt lề tab không hiển thị chính xác trên một số trình duyệt (chúng tôi cũng đã chuyển trở lại thành không xác định các dòng được bao bọc; trước đây chúng tôi đã cố gắng duy trì mức thụt lề của dòng đầu tiên và sẽ tiếp tục khám phá điều này)
• MỚI: Tùy chọn của người dùng mới **Chiều cao dòng nhỏ gọn **cho phép bạn chọn chiều cao dòng nhỏ gọn hơn. Bạn có thể chuyển đổi nó từ menu cài đặt chế độ xem (⚙️) gần đầu trang.

Màn hình.Ghi âm.2024-09-26.at.11.34.46. AM.mov

Tìm hiểu thêm về chiều cao đường nhỏ gọn

[uberzerg9]

Hello Github Developers, we got some issue with dates of old commits (for today is Mon 9 Dec 2024), here is example:
https://bytebucket.org/Dimanegara/workspace/snippets/pqBqBy/raw/eaaf43da13339d0b8f39413cd2469627db2520f4/Screenshot%202024-12-09%20at%2016.46.20.png?token=f3d777d883a69b334580274e96beeaf4170d8617 - As you can see on screenshot, the last commit was 18 day ago (now Date is Mon 9 Dec 2024), but If we open his last commit - https://bytebucket.org/Dimanegara/workspace/snippets/4qpqpd/raw/b59ee0a6a49f72e7b04b62dd67ca7ee4599ff194/Screenshot%202024-12-09%20at%2016.51.39.png?token=7d0d4a9bb650dd8d60270b861aebad7029c2730d - we can see, that this commit was implemented at Jan 26 2024 (other commits before Jan 26 2024 - https://bytebucket.org/Dimanegara/workspace/snippets/XEzEz9/raw/c93467c12bc278c9d97e1efd86daafd750947abf/Screenshot%202024-12-09%20at%2016.53.17.png?token=fbd83bae104f94646b228477d0c47515e9c14528)

[vanaigr]

Images are clipped and jump around:

output.mp4

[ericoporto]

Going back on chrome on iPhone doesn’t go to the commit history. Chrome on iPhone badly implements a weird heuristic to figure where to go back. It would be nice to have a button to go back to the list of commits for the branch that took me there or to fix the history to work with google chrome on iPhone

whatwg/html#7832

[MasterInQuestion]

    Input the URL directly for navigation should workaround?

[ericoporto]

Not really, it will require a ton more of typing to retype the url in the browser

[darikprescott]

Hey has anyone  contacted me ??? i have not once been in discussion with anyone!!!!    SSH login On Wednesday, December 11, 2024 at 02:27:29 PM CST, almao ***@***.***> wrote: i would dude. b id believe that might be reverse engineering? 3rd patries etc... ive been in alfpa and some beta. Im SHURE one of the Githubstaff would help you out. U mind explaining whats up btw? was away for an frew hours — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[VahidRafieiPour]

ای که بر مرکب تازنده سواری هشدار خر مسکین سوخته در آب گل است

…

-------- پیام نخستین -------- از: DARIK R PRESCOTT ***@***.***> ارسال: ۱۲ دسامبر ۲۰۲۴ ۰۶:۰۶:۵۹ (GMT+03:30) به: community/community ***@***.***> رونوشت به: ***@***.***" ***@***.***>, Manual ***@***.***> موضوع: Re: [community/community] New commit details page (public beta) feedback (Discussion #139005) Hey has anyone  contacted me ??? i have not once been in discussion with anyone!!!!    SSH login On Wednesday, December 11, 2024 at 02:27:29 PM CST, almao ***@***.***> wrote: i would dude. b id believe that might be reverse engineering? 3rd patries etc... ive been in alfpa and some beta. Im SHURE one of the Githubstaff would help you out. U mind explaining whats up btw? was away for an frew hours — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

-- Reply to this email directly or view it on GitHub: #139005 (comment) You are receiving this because you are subscribed to this thread. Message ID: ***@***.***>