summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJan Provaznik <jprovaznik@gitlab.com>2018-10-16 13:33:25 +0200
committerJan Provaznik <jprovaznik@gitlab.com>2018-10-16 13:33:25 +0200
commit5fa781ecf7785d74a226a6862c1093c25004b4b1 (patch)
treedf0b048430c9ab7ca1250dd947f0499f4a9376f2
parentb69a047409d035aa69f8018cea2a86884e0530fd (diff)
downloadgitlab-ce-5fa781ecf7785d74a226a6862c1093c25004b4b1.tar.gz
Fix "ready for review" link
Remove assignee_id=0 condition from search filters, we agreed that just presence of "ready of review" label is sufficient for filtering MRs, no need to unassign yourself.
-rw-r--r--doc/development/code_review.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/code_review.md b/doc/development/code_review.md
index 87437dd7720..4bbcdc6329f 100644
--- a/doc/development/code_review.md
+++ b/doc/development/code_review.md
@@ -109,7 +109,7 @@ It is responsibility of the author of a merge request that the merge request is
### List of merge requests ready for review
-Developers who have capacity can regularly check the list of [merge requests to review](https://gitlab.com/groups/gitlab-org/-/merge_requests?scope=all&utf8=%E2%9C%93&state=opened&label_name%5B%5D=ready%20for%20review&assignee_id=0) and assign any merge request they want to review.
+Developers who have capacity can regularly check the list of [merge requests to review](https://gitlab.com/groups/gitlab-org/-/merge_requests?scope=all&utf8=%E2%9C%93&state=opened&label_name%5B%5D=ready%20for%20review) and assign any merge request they want to review.
### Reviewing code