Hi, and first off, thanks for gogs! I've been using it to host my private projects for a few years now, and the footprint is amazing. Plus, it has everything I really need - well, until I grew new needs recently, which is what this proposal is about.

There's one thing I've grown to really enjoy from using GitLab at work: The ability to easily go commit by commit when reviewing.

Here's how that works there: If you click a commit on the commits tab in a merge request, instead of the generic detail view for that commit, you see the diff for just that commit in the changes tab. If the MR contains multiple commits, there are arrow buttons to go forwards/backwards, and a button to see the diff for the entire MR again. GitHub has the same functionality, but all in the commits tab.

This meshes extremely well with an alternative to small, self-contained PRs where those aren't feasible: larger PRs with small, self-contained commits that have been curated via interactive rebases/history editing. Going commit by commit really shines here - it's like doing multiple bite-sized reviews in quick succession instead of wrapping your head around the entire changeset all at once.

And here's the kicker: the fact that the UI for this is so good/accessible turned using that from a desperation move to understand PRs that should have been split up into multiple PRs into just my standard workflow. commits -> <first commit> is two clicks to get going vs the one click for changes, and I get so much more info. Even if the commits document the development process instead of being curated, decomposing the process into smaller steps this way is huge.

In gogs, the next best thing I found is commits -> <open them all in a new tab and use your browser to navigate>. That kinda works for me, but I won't be doing it as often, and it's an odd thing to ask collaborators to do. If it's accessible and a standard workflow, I can justify asking people to use it and adjusting my metric for how much is too much in a PR.

I realize that gogs is deliberately lean, and understand if doing things as specific this is considered a non-goal. But I've also been wanting to get my hands dirty with Go. If something like this is deemed worthwhile, depending on the requirements/how exactly y'all would want this done, I'd consider doing it. Can't make promises right now, but it would be nice to know if this is an option.