diff options
| author | Emil Velikov <[email protected]> | 2019-02-25 11:57:20 +0000 |
|---|---|---|
| committer | Emil Velikov <[email protected]> | 2019-02-26 11:27:10 +0000 |
| commit | 40a82e6463f2686b262cdb1dad067646c47d4469 (patch) | |
| tree | a6286b0fd624df6a35c6dfe148b3dc06a9eab5b7 /docs/submittingpatches.html | |
| parent | d9d1cb43d7e28b62a3993f3cd4b7dd0972892006 (diff) | |
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 <[email protected]>
Cc: Dylan Baker <[email protected]>
Signed-off-by: Emil Velikov <[email protected]>
Reviewed-by: Eric Engestrom <[email protected]>
Reivewed-by: Erik Faye-Lund <[email protected]>
Diffstat (limited to 'docs/submittingpatches.html')
| -rw-r--r-- | docs/submittingpatches.html | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/docs/submittingpatches.html b/docs/submittingpatches.html index 137e39c925d..65af32d4bba 100644 --- a/docs/submittingpatches.html +++ b/docs/submittingpatches.html @@ -237,6 +237,11 @@ your email administrator for this.) </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 in your patches. There should not be "fixup" patches in the history. |