4 ms·
Ugh I hear you. I have been following this issue for nearly a year: https://gitlab.com/gitlab-org/gitlab-ce/issues/39056 https://gitlab.com/gitlab-org/gitlab-ce
by apple4ever 8y ago
Ugh I hear you. I have been following this issue for nearly a year: https://gitlab.com/gitlab-org/gitlab-ce/issues/39056 https://gitlab.com/gitlab-org/gitlab-ce/issues/39056
I cannot believe its not fixed it. They made the MR file view completely useless for us. It was a new "feature" that actually made things worse.
- detaro 8y agoAlso sad to see how reports about regressions appear to turn into "feature requests", that then are nice to have instead of important.
- jramsay 8y agoJames (Product Manager at GitLab) here. I've just picked up merge requests and have seen lots of feedback across multiple issues related to navigating between diffs/files when reviewing a merge request, and I want to make it better too. There have been a few different solutions proposed including adding a file tree to the merge request interface, so you can quickly see a full list of the files and how they relate to each other. There is a design discovery issue for adding a file tree to the merge request interface https://gitlab.com/gitlab-org/gitlab-ce/issues/49189 https://gitlab.com/gitlab-org/gitlab-ce/issues/49189 scheduled for the next release to work out the UX in more detail. Would a file tree make reviewing a merge request easier for you? Thanks for the feedback, and would love to hear more here, or on the issue.