docs: mention "Allow commits from members who can merge..."

Mention the tick-box otherwise only the MR author can rebase the series.

Cc: Jordan Justen <jordan.l.justen@intel.com>
Cc: Dylan Baker <dylan@pnwbakers.com>
Signed-off-by: Emil Velikov <emil.velikov@collabora.com>
Reviewed-by: Eric Engestrom <eric.engestrom@intel.com>
Reivewed-by: Erik Faye-Lund <erik.faye-lund@collabora.com>

diff --git a/docs/submittingpatches.html b/docs/submittingpatches.html
index 137e39c925d2aa36f5bafad32a1a2087b9dfc210..65af32d4bba986a76398daee971880ca8b041fa4 100644 (file)
--- a/docs/submittingpatches.html
+++ b/docs/submittingpatches.html
@@ -236,6 +236,11 @@ your email administrator for this.)
     <li>Other tag examples: gallium, util
   </ul>
 </p>
+<p>
+  Tick the following when creating the MR. It allows developers to
+  rebase your work on top of master.
+  <pre>Allow commits from members who can merge to the target branch</pre>
+</p>
 <p>
   If you revise your patches based on code review and push an update
   to your branch, you should maintain a <strong>clean</strong> history