Incoming MR code changes
For large projects such as GitLab CE/EE, we have a lot of MRs being reviewed and merged daily. Sometimes there are MRs with code that conflict against each other. Typically, the MR that didn't make it into
master first, will have to either fix massive conflicts or re-implement certain features. There was a time where someone thought a certain piece of code wasn't being used in multiple places, so it was refactored out of the
util file but an incoming MR needed it in the
I'm not sure how this would look like, but it would be fantastic if there was a way MRs could intelligently detect what code changes are coming from other open MRs. This would inform both the reviewer and the MR author what changes are incoming to the
master branch. This would primarily help reviewers (instead of having to remember the different related MRs) easily determine which MRs should be merged first so that conflicts are minimized. And would lead to decreased cycle time from idea to production!