ConfigTypes Module
Types and nested modules
| Type/Module | Description |
|
|
|
|
|
|
|
|
|
|
Contains default configuration values and settings used across the application. This module provides default strategies, configurations, and mappings related to various components such as file splitting, output paths, versioning, commit grouping, and release generation. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Convenience active patterns to elicit specific settings from a |
|
|
|
|
|
Management strategy for |
|
|
Bumping related configuration. |
|
|
Strategies for determining whether a commit will result in a specified bump type. |
|
|
A mapping of strategies to the bump types (Epoch, Major, Minor, Patch). |
|
|
Configuration of commit related options. |
|
|
Epoch matcher can only be used to match a footer key. The value of the footer is then used as the new epoch name. Remember that casing is not used in matching footers as per the conventional commit spec. |
|
|
|
|
|
|
|
|
|
|
|
The GitNet configuration container. |
|
|
Github configuration and settings. |
|
|
Indicates how to determine the Github URL. |
|
|
Single case DU of a commit group with the list of matching strategies. |
|
|
Commit ignore strategies. See Remarks for overview. |
|
|
Network configuration, for git services such as GitHub, GitLab, GitBucket etc (only GitHub implemented atm). |
|
|
Configuration for the changelog/releasenotes output. |
|
|
|
|
|
|
|
|
|
Partas.GitNet