User Experience for Comments on Individual Commits

[kaofelix]

Select Topic Area

Product Feedback

Body

Hi GitHub community! Not sure if this is the right category to talk about this, but thought it was close enough. Let me know if I should move this elsewhere.

Our team is using a Trunk Based Development workflow without PRs. We still review and give feedback to each other's code, but the mechanism we use is mainly comments on individual commits. As a workflow this works very well for us, the only real issue is that the current user experience for comments on individual commits makes this much harder than it needs to be.

For example, in the file list we can see the speech bubble telling us that there's a comment:

However, there's no way to interact with it. I tried to click it more than once expecting it would lead me to where the comment is, but it doesn't do anything. I have to scroll around and find where the comment is, and it's inside this really really subtle little avata circle thing that I have to click to see a comment thread:

I also had a few bugs where I opened one thread, closed it and when trying to open a second one, nothing would happen and I had to refresh the page and go through the same process of hunting down the comment I'm looking for.

The PR comment experience is a lot better and I don't see why the commit comments just can't work exactly the same, where comments appear prominently under the line they are commenting on. My assumption is that if someone is using comments in commits they are important enough to deserve a bit more prominence.

Anyway, happy to hear anyone else's thoughts and tips on this!

[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. ⭐

[rcoopr]

Visibility for commit comments is bad, agreed. Also regularly experience those bugs with an opened comment making it impossible to open another comment

[kaofelix]

Looks like this got massively improved recently! https://github.blog/changelog/2025-05-15-commit-details-page-may-updates/