include markdown docs changes

Author: gittools-bot

docs/input/docs/reference/configuration.md

@@ -209,8 +209,10 @@ branches:
 ignore:
   sha: []
   paths: []
+  tags: []
+  branches: []
 ```
-<sup><a href='/docs/workflows/GitFlow/v1.yml#L1-L168' title='Snippet source file'>snippet source</a> | <a href='#snippet-/docs/workflows/GitFlow/v1.yml' title='Start of snippet'>anchor</a></sup>
+<sup><a href='/docs/workflows/GitFlow/v1.yml#L1-L170' title='Snippet source file'>snippet source</a> | <a href='#snippet-/docs/workflows/GitFlow/v1.yml' title='Start of snippet'>anchor</a></sup>
 <!-- endSnippet -->
 
 The supported built-in configuration for the `GitHubFlow` workflow (`workflow: GitHubFlow/v1`) looks like:
@@ -335,8 +337,10 @@ branches:
 ignore:
   sha: []
   paths: []
+  tags: []
+  branches: []
 ```
-<sup><a href='/docs/workflows/GitHubFlow/v1.yml#L1-L117' title='Snippet source file'>snippet source</a> | <a href='#snippet-/docs/workflows/GitHubFlow/v1.yml' title='Start of snippet'>anchor</a></sup>
+<sup><a href='/docs/workflows/GitHubFlow/v1.yml#L1-L119' title='Snippet source file'>snippet source</a> | <a href='#snippet-/docs/workflows/GitHubFlow/v1.yml' title='Start of snippet'>anchor</a></sup>
 <!-- endSnippet -->
 
 The preview built-in configuration (experimental usage only) for the `TrunkBased` workflow (`workflow: TrunkBased/preview1`) looks like:
@@ -446,8 +450,10 @@ branches:
 ignore:
   sha: []
   paths: []
+  tags: []
+  branches: []
 ```
-<sup><a href='/docs/workflows/TrunkBased/preview1.yml#L1-L102' title='Snippet source file'>snippet source</a> | <a href='#snippet-/docs/workflows/TrunkBased/preview1.yml' title='Start of snippet'>anchor</a></sup>
+<sup><a href='/docs/workflows/TrunkBased/preview1.yml#L1-L104' title='Snippet source file'>snippet source</a> | <a href='#snippet-/docs/workflows/TrunkBased/preview1.yml' title='Start of snippet'>anchor</a></sup>
 <!-- endSnippet -->
 
 The details of the available options are as follows:
@@ -674,31 +680,6 @@ ignore:
 Ignoring a tag does not ignore the commit it points to. The commit remains part
 of version calculation and can still be reached through other references.
 
-#### branches
-
-A sequence of regular expressions matching branch names that should not be used
-as auxiliary [version sources][version-sources]. Patterns are matched
-case-insensitively against the branch name without the local or remote prefix,
-so `release/old` and `origin/release/old` are treated as the same branch.
-Multiple patterns use OR semantics, and `^` and `$` can be used to anchor a
-match.
-
-```yaml
-ignore:
-  branches:
-    - ^experimental/
-    - ^release/old$
-```
-
-The current branch, or an explicitly selected target branch, remains eligible
-even when its name matches. On a build server, ignored remote-tracking branches
-are not created or updated as local branches during normalization. Existing
-local branches are left untouched. Only references available in the repository
-can be matched.
-
-Ignoring a branch does not ignore commits reachable from that branch. Shared
-history and tags on shared commits remain eligible for version calculation.
-
 #### paths
 
 A sequence of regular expressions that represent paths in the repository. Commits that modify these paths will be excluded from version calculations. For example, to filter out commits that belong to `docs`: