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
Is there an existing issue or pull request for this?
I have searched the existing issues and pull requests
Feature description
changelog.postprocessors and git.commit_preprocessors work on the entire changelog or git message respectively. The documentation does not clearly describe this. As a first time user, one might expect that either processor only affects the part of the input that actually matches the pattern.
For example, a postprocessor like the following would be expected to replace all occurrences of <REPO> with https://github.com/orhun/git-cliff. It replaces the entire changelog instead.
The documentation should be revised in all places to clearly state that pattern does not limit the scope of the replacement, but instead is only used to check if a given string is supposed to replaced entirely.
Alternatives considered
None
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue or pull request for this?
Feature description
changelog.postprocessors
andgit.commit_preprocessors
work on the entire changelog or git message respectively. The documentation does not clearly describe this. As a first time user, one might expect that either processor only affects the part of the input that actually matches thepattern
.For example, a postprocessor like the following would be expected to replace all occurrences of
<REPO>
withhttps://github.com/orhun/git-cliff
. It replaces the entire changelog instead.Desired solution
The documentation should be revised in all places to clearly state that
pattern
does not limit the scope of the replacement, but instead is only used to check if a given string is supposed to replaced entirely.Alternatives considered
None
Additional context
No response
The text was updated successfully, but these errors were encountered: