GitHub commit page does not render all changed file diffs for one repository

[akshay-820]

🏷️ Discussion Type

Bug

Body

Repository:
https://github.com/akshay-820/ClubSphere

Example commit:
akshay-820/ClubSphere@c487d69

I'm seeing what appears to be a GitHub web UI issue with the commit page.

Issue

The commit page reports 7 files changed. The left file tree correctly lists all 7 changed files, but only the first few file diffs are rendered.
The remaining files appear in the sidebar, but clicking them only changes the URL to the corresponding #diff-... anchor and no diff is displayed.

Expected behavior -

Clicking any file in the sidebar should display its diff.

Actual behavior -

Only a subset of the changed file diffs are rendered.

What I've verified :

• git show <commit> locally displays the complete diff.
• The .patch and .diff endpoints for the same commit contain the complete diff.
• The repository's Code view opens all files normally.
• The issue reproduces across multiple browsers.
• The repository has no submodules and only one .git directory.
• git fsck --full reports no repository corruption.

Additional observations :

• This issue appears to be repository-specific.
• It occurs on multiple commit pages within this repository.
• Other repositories under the same GitHub account display commit diffs correctly.
• The problem is limited to the GitHub commit page renderer for this repository.

Steps to reproduce :

1. Open the example commit.
2. Observe that the page reports 7 files changed.
3. Click one of the server files in the left sidebar (for example, membershipController.ts).
4. The URL changes to the corresponding #diff-... anchor, but the diff is not displayed.

CAN SOMEONE PLEASE HELP ME OUT?

I've attached screenshots showing:

• the GitHub commit page listing all changed files but rendering only some diffs.

• git show locally displaying the diff for one of the files that GitHub does not render.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[L-Clouds]

I'm seeing this too, on a different repo of course, and just came here to figure out if it was only me.

[AgentOak]

I've stumbled upon the same issue in multiple repositories, at least since the beginning of this week, maybe longer.
I can confirm the issue for the repository/commit you linked, only two files displayed.

Also, even for files that are rendered, clicking the file name in the list to jump to the diff doesn't work.

[asill01]

I'm seeing the same thing - and I've tried all sorts of different scenarios to rule things out. I'm seeing this issue while trying all of the following:

• Across all repositories (private and public)
• Whether or not I'm logged in to GitHub
• With/without VPN on
• 4 different browsers
• 2 different home wireless networks and tried using a cell network (browser on my phone)
• 3 different computers - PC, Windows Laptop, and a Mac

NOTE: Diffs appear to work in the GitHub app, so it appears to be specific to web browsers

Also - I'm aware that using "compare" to compare a commit against itself shows the whole diff (instead of looking at at the actual commit). But this is a work-around, and not a fix.

[akshay-820]

Thank you so much for the workaround

[Sculas]

I'm seeing this as well on my own private repositories (haven't checked elsewhere yet).

[Sammy-T]

Looks like I'm having the same issue.

[damianniebler]

Same issue, please fix.

[dbry]

Just started seeing this myself yesterday. If the diffs are short they show up, but longer ones don't, although they're listed in the left "Filter files..." pane.

Don't know if this is new also, but clicking on the files in the left pane doesn't seem to do anything, even when everything is working fine. I can see that the URLs are different, but no changes show up. If that worked, it might be a way to see file diffs that aren't showing up, but no.

Here's a couple examples. The first commit shows no file diffs, but there is a single changed file. If you look quickly it seems that the diffs are about to show, then they disappear. There's no message indicating a binary file was detected or the diff was too big (and the module is only about 400 lines).

dbry/DXD-e@847d816

Here's a more interesting one. The first two files show up with diffs, but the next five don't even though they're in the listed files to the left (and clicking there does nothing).

dbry/DXD-e@468654d

Thanks!