You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/input/docs/reference/configuration.md
-18Lines changed: 0 additions & 18 deletions
Original file line number
Diff line number
Diff line change
@@ -624,24 +624,6 @@ Date and time in the format `yyyy-MM-ddTHH:mm:ss` (eg `commits-before:
624
624
2015-10-23T12:23:15`) to setup an exclusion range. Effectively any commit before
625
625
`commits-before`will be ignored.
626
626
627
-
#### paths
628
-
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`:
629
-
```yaml
630
-
ignore:
631
-
paths:
632
-
- ^docs\/
633
-
```
634
-
This ignore config can also be used to filter only those commits that belong to a specific project in a monorepo. For GitVersion to consider only commits that are part of subdirectory called `projectA`, use a regex that matches all paths except those starting with `ProjectA`:
635
-
```yaml
636
-
ignore:
637
-
paths:
638
-
- ^(?!ProjectA).*$
639
-
```
640
-
641
-
::: {.alert .alert-warning}
642
-
A commit is ignored by the `ignore.paths` configuration only if **all paths** changed in that commit match one of the specified regular expressions. If any file in the commit does not match an ignore pattern, the commit will be included in version calculations.
643
-
:::
644
-
645
627
### merge-message-formats
646
628
647
629
Custom merge message formats to enable identification of merge messages that do not
0 commit comments