Review of large merge request is error-prone
Problem Statement
Reviewing code contribution for software engineers, maintainers, and team leads is a critical daily task.
They need an efficient tool that allow quickly identify and follow changes. This is especially true when reviewing a merge request, which may change quickly with complex changes and contributions.
The current diff view of merge request is cumbersome because it contains too many information at the same time, confusing reviewer when they need to focus on a specific part of the code contribution.
This is caused by two mains problems, focusing in the Changes tab of a merge request:
- The order of files in the tree view is not always the same as in the infinite scrolling panel on the right.
- The infinite scrolling makes a reviewer confusing and makes it difficult to quickly identify the start and end of a file diff.
Solution suggestion
A possible solution could be to present only one file at a time in the diff panel aside the tree view, possbily allowing to customize the expected view with diff setting options.
Reach
Targeted people:
- Development Team Lead
- Software Engineer
- Security Analyst
6.0 = Impacts a large percentage (~50% to ~80%) of the above.
Impact
3.0 = Massive impact
Confidence
100% = High confidence
Effort
To be defined by the developer team. We are a customer.