From 67a712f95ccc94eb7c703082d3577070552ee0d8 Mon Sep 17 00:00:00 2001 From: Sebastian Krebs Date: Fri, 12 May 2023 10:08:33 +0200 Subject: [PATCH] fix: alphabetical order --- docs/usage/configuration-options.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/usage/configuration-options.md b/docs/usage/configuration-options.md index dd4c59ee173ddc..12d1eeae5befe4 100644 --- a/docs/usage/configuration-options.md +++ b/docs/usage/configuration-options.md @@ -448,6 +448,11 @@ Check out the default value for `commitMessage` to understand how this field is This is used to alter `commitMessage` and `prTitle` without needing to copy/paste the whole string. The "extra" is usually an identifier of the new version, e.g. "to v1.3.2" or "to tag 9.2". +## commitMessageLowerCase + +With `semanticCommits` pr- and commit-titles will by default (`"auto"`) be converted to all-lowercase. +Set this to `"never"` to leave the titles untouched, allowing uppercase characters in semantic commit titles. + ## commitMessagePrefix This is used to alter `commitMessage` and `prTitle` without needing to copy/paste the whole string. @@ -3310,11 +3315,6 @@ If configured to `enabled`, then the `semanticCommitScope` and `semanticCommitTy Renovate autodetects if your repository is already using semantic commits or not and follows suit, so you only need to configure this if you wish to _override_ Renovate's autodetected setting. -## commitMessageLowerCase - -With `semanticCommits` pr- and commit-titles will by default (`"auto"`) be converted to all-lowercase. -Set this to `"never"` to leave the titles untouched, allowing uppercase characters in semantic commit titles. - ## separateMajorMinor Renovate's default behavior is to create a separate branch/PR if both minor and major version updates exist (note that your choice of `rangeStrategy` value can influence which updates exist in the first place however).