wip

Author: bearomorphism

docs/config/bump.md

@@ -0,0 +1,40 @@
+# Bump Options
+
+## `version_files`
+
+- Type: `list`
+- Default: `[]`
+
+Files (or glob patterns) where the version will be updated. A pattern to match a line, can also be specified, separated by `:`.
+See [Version Files](../commands/bump.md#version_files) for more details.
+
+
+## `version_scheme`
+
+- Type: `str`
+- Default: `pep440`
+
+Select a version scheme from the following options:
+
+- `pep440`
+- `semver`
+- `semver2`
+
+Useful for non-python projects. See [Version Schemes](../commands/bump.md#version-schemes-version-scheme) for more details.
+
+
+### `tag_format`
+
+- Type: `str`
+- Default: `$version`
+
+Format for the git tag, useful for old projects, that use a convention like `"v1.2.1"`. [Read more][tag_format]
+
+### `legacy_tag_formats`
+
+- Type: `list`
+- Default: `[]`
+
+Legacy git tag formats, useful for old projects that changed tag format.
+Tags matching those formats will be recognized as version tags and be included in the changelog.
+Each entry uses the syntax as [`tag_format`](#tag_format). [Read more][tag_format]

docs/config/option.md

@@ -16,48 +16,12 @@ Name of the committing rules to use.
 
 Current version. Example: `"0.1.2"`. Required if you use `version_provider = "commitizen"`.
 
-### `version_files`
-
-- Type: `list`
-- Default: `[]`
-
-Files (or glob patterns) where the version will be updated. A pattern to match a line, can also be specified, separated by `:` [Read more][version_files]
-
 ### `version_provider`
 
 - Type: `str`
 - Default: `commitizen`
 
-Version provider used to read and write version. [Read more][version-provider]
-
-### `version_scheme`
-
-- Type: `str`
-- Default: `pep440`
-
-Select a version scheme from the following options:
-
-- `pep440`
-- `semver`
-- `semver2`
-
-Useful for non-python projects. [Read more][version-scheme]
-
-### `tag_format`
-
-- Type: `str`
-- Default: `$version`
-
-Format for the git tag, useful for old projects, that use a convention like `"v1.2.1"`. [Read more][tag_format]
-
-### `legacy_tag_formats`
-
-- Type: `list`
-- Default: `[]`
-
-Legacy git tag formats, useful for old projects that changed tag format.
-Tags matching those formats will be recognized as version tags and be included in the changelog.
-Each entry uses the syntax as [`tag_format`](#tag_format). [Read more][tag_format]
+Version provider used to read and write version. See [Version Provider](./version_provider.md) for more details.
 
 ### `ignored_tag_formats`
 
@@ -243,7 +207,6 @@ Provide custom changelog jinja template path relative to the current working dir
 Provide extra variables to the changelog template. [Read more][template-customization]
 
 
-[version_files]: ../commands/bump.md#version_files
 [tag_format]: ../commands/bump.md#tag_format
 [bump_message]: ../commands/bump.md#bump_message
 [major-version-zero]: ../commands/bump.md#-major-version-zero

docs/tutorials/tag_format.md

@@ -43,7 +43,7 @@ As a result, the tag generated on bump will have this format: `v1.0.0` and the v
     Both `$version` and `${version}` syntaxes are strictly equivalent. You can use the one you prefer.
 
 See [the `version_scheme` section in `bump` command documentation](../commands/bump.md#version_scheme) for more details on version schemes and how to define your own.
-See [`tag_format`](../config/option.md#tag_format) and [`version_scheme`](../config/option.md#version_scheme) settings in [Configuration reference](../config/option.md) for more details on these settings.
+See [`tag_format`](../config/option.md#tag_format) and [`version_scheme`](../config/bump.md#version_scheme) settings in [Configuration reference](../config/option.md) for more details on these settings.
 
 ## Changing convention
 

mkdocs.yml

@@ -45,6 +45,7 @@ nav:
   - Configuration:
       - Configuration File: "config/configuration_file.md"
       - Version Provider: "config/version_provider.md"
+      - Bump Options: "config/bump.md"
       - Settings: "config/option.md"
   - Customization: "customization.md"
   - Tutorials: