Replace Close with Reject for Merge Requests

Problem to solve

Confusion between rejecting and merging a merge request.

Frequently members of my team will fill in the comment box and select the comment and close button, believing this to be the correct action to take when intending to merge the code.

Target audience

• Parker, Product Manager, https://design.gitlab.com/research/personas#persona-parker

This impacts general usability

Further details

N/A

Proposal

I suggest replacing all occurrences of Close with Reject with regards to merge requests. This should make it clearer that the action that button takes does not merge the branches.

What does success look like, and how can we measure that?

Success would be fewer merge requests having to be re-opened because the original intent was actually to merge. Hard to know for sure how you might measure that accurately.

Links / references