(UX) Commit view only shows 20 files at once and is hard to browse
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
The commit view only shows 20 files at a time, and the current implementation has two major UX issues:
- You can't see which files are in the commit.
- You can't go to a given file.
... without paging through. And of course you can page through and Ctrl+F on each page, but that's horribly inefficient.
Sample commit view
Can't see which files are in the commit
When a user is viewing a commit, they may want to know if a given file is changed in this commit. However, the Commit View doesn't present them with a full list of files that this commit changes. They can only see 20 at a time.
Can't go to a given file
Perhaps more common --- the user finds a commit by exploring a Blame or a file's History so they know a certain file was changed in this commit, but how do they go to it? There is no index to jump them to the file by name. There is only the current page (which may or may not contain the file), and the pagination.
So they have to page through, and check every page for the file! This is really hard to use.
Possible solutions:
- Give the commit view a file listing like the MR diff view.
- Make the File search field search all files, not just the current 20.
Are these UX issues already on the radar, by any chance?
Link to my forum post that got no response (https://forum.gitlab.com/t/commit-view-ux/74801)