Merge conflict early warning
Right now you see a merge conflict only when someone else merged into the target branch.
It would be great to get an earlier heads-up that your work is not compatible. This way you can coordinate with the other author early instead of both continuing and one of you ending up with having to resolve a giant merge conflict later on.
The warning can be in the form of an email, terminal message, todo, and/or warning on your merge request.
It can be based on the target of your merge request and/or assume the default branch when a feature branch exists without a merge request.
It can run on push to a feature branch or be run async in a background job.
Links / references
Edited by James Ramsay (ex-GitLab)