From da04fdcf6e87e78b398cd2d7ddca0988c1b0ee1f Mon Sep 17 00:00:00 2001 From: Rhys Arkins Date: Thu, 4 Nov 2021 14:25:21 +0100 Subject: [PATCH] Update docs/usage/configuration-options.md Co-authored-by: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com> --- docs/usage/configuration-options.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/usage/configuration-options.md b/docs/usage/configuration-options.md index 99928befe9549a..049774b458ac85 100644 --- a/docs/usage/configuration-options.md +++ b/docs/usage/configuration-options.md @@ -1679,7 +1679,7 @@ It falls back to Renovate-based automerge if the platform-native automerge is no You can also fine-tune the behavior by setting `packageRules` if you want to use it selectively (e.g. per-package). -Note that the outcome of `rebaseWhen=auto` can differ when `platformAutomerge=true` is enable. +Note that the outcome of `rebaseWhen=auto` can differ when `platformAutomerge=true`. Normally when you set `rebaseWhen=auto` Renovate rebases any branch that's behind the base branch automatically, and some people rely on that. This behavior is no longer guaranteed when you enable `platformAutomerge` because the platform might automerge a branch which is not up-to-date. For example, GitHub might automerge a Renovate branch even if it's behind the base branch at the time.