This repository has been archived by the owner on Aug 6, 2021. It is now read-only.
update.Group #2
Merged
update.Group #2
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
Batches were one-dimensionally about clustering updates together into a single branch. I want to do some per-path configuration flags (specifically: I only want AWS PRs weekly!), so leaving this as a placeholder.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 replaces the v0 of batching updates from thepwagner/action-update-go#53 .
That was a cool experiment, but I'd like to be able to attach configurations to each cluster of updates instead of just grouping updates together.
Aside from the name change,
batcheswere exclusively path prefixes while groups support regular expressions.The first usable bit of configuration is
range, which can be used to filter versions allowed. There's an accepted bias towards semver: ranges are defined using>= v1.2.3syntax.The range implementation is functional but super inefficient.
There's a placeholder for
frequency, which is what I'm really after.Being Actions means I need the
scheduleto trigger every day, for frequency of security updates. But there are some pages that I don't want a daily PR for (aws-sdk-goI'm looking at you).