Do not use MR abbreviation in "Thread the conversations through all stages"
1 unresolved thread
1 unresolved thread
The abbreviation "MR" can be easily understood by people using GitLab, but difficult for the rest of the world.
Merge request reports
Activity
added 1 commit
- b3f5233c - Let's just use "pull requests" instead of "Pull Requests (Merge Requests)"
18 18 %h3 Link everything 19 19 20 20 %p 21 Make sure ideas are linked to issues, issues to MR's, MR's to deployments, deployments to monitoring.<br/> 21 Make sure ideas are linked to issues, issues to pull requests, pull requests to deployments, deployments to monitoring.<br/> @sytses what do you think? Adam suggested "Merge requests (Pull Requests)" first, but it adds too much noise, since we had to repeat it twice.
I think "merge requests" is fine on its own. I imagine anyone familiar with the term "pull request" should be able to figure out that they're actually requesting a merge.
Edited by username-removed-1163502
Please register or sign in to reply