Allow customizing patch automerge behavior for selected dependencies #107
+49
−6
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
simu
force-pushed
the
feat/configurable-patch-automerge
branch
from
54fb4bd to
f37f565
Compare
We introduce a new cookiecutter argument which allows users to specify zero or more regex patterns for dependencies whose patch level updates shouldn't be automerged. The template expects that the contents of the new argument is a string which contains zero or more regex patterns separated by semicolons. The template will use these patterns as the values for the package rule field `excludePackagePatterns`.
simu
force-pushed
the
feat/configurable-patch-automerge
branch
from
f37f565 to
f58f61e
Compare
simu
changed the title
…encies This commit introduces a new cookiecutter argument `automerge_patch_v0_regexp_allowlist` which can be used to selectively enable patch automerging for v0.x dependencies. The template expects that the content of the new argument is a string which contains zero or more regexp patterns separated by semicolons. If global automerging of patch updates for v0.x dependencies is disabled, but `automerge_patch_v0_regexp_allowlist` isn't empty, the template generates an additional package rule that enables automerge only for dependencies that are currently v0.x and which match one of the patterns provided in the argument. This rule is not required and therefore not generated when `automerge_patch_v0` is enabled. If you want to disable automerging for some v0.x patch level updates but automerge patch level updates for v0.x dependencies by default, you can specify patterns for which patch level updates shouldn't be automerged in cookiecutter argument `automerge_patch_regexp_blocklist`.
simu
force-pushed
the
feat/configurable-patch-automerge
branch
from
4a11211 to
e67a246
Compare
bastjan
approved these changes
Jun 7, 2024
Move default configuration that's shared between all rules into a function instead of repeating the raw dict for each rule.
simu
force-pushed
the
feat/configurable-patch-automerge
branch
from
8c41775 to
bb95794
Compare
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces a new cookiecutter argument which allows users to specify zero or more regex patterns for dependencies whose patch level updates shouldn't be automerged.
The template expects that the contents of the new argument is a string which contains zero or more regex patterns separated by semicolons. The template will use these patterns as the values for the package rule field
excludePackagePatterns.Additionally, this PR introduces a new cookiecutter argument
automerge_patch_v0_regexp_allowlistwhich can be used to selectively enable patch automerging for v0.x dependencies.The template expects that the content of the new argument is a string which contains zero or more regexp patterns separated by semicolons.
If global automerging of patch updates for v0.x dependencies is disabled, but
automerge_patch_v0_regexp_allowlistisn't empty, the template generates an additional package rule that enables automerge only for dependencies that are currently v0.x and which match one of the patterns provided in the argument.This package rule is not required and therefore not generated when
automerge_patch_v0is enabled. If you want to disable automerging for some v0.x patch level updates but automerge patch level updates for v0.x dependencies by default, you can specify patterns for which no patch level updates should be merged in cookiecutter argumentautomerge_patch_regexp_blocklist.Checklist
changelog.
The PR has a meaningful description that sums up the change. It will be
linked in the changelog.
bug,enhancement,documentation,change,breaking,dependencyas they show up in the changelog.