Add tests for pullRequests.grouping
syntax
#3654
Open
+48
−0
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.
A colleague mentioned to me that some of our
pullRequests.grouping
were not pulling in all the artifacts we were expecting - while looking into this, I realised that I wasn't 100% clear on where wildcards could be used inpullRequests.grouping
, so I wrote this test to exercise all the cases that were relevant to us, and see what worked - this may be tested elsewhere to some extent in the Scala Steward codebase, but I think it's helpful to drill into the specific functionality with these new tests onPullRequestUpdateFilter
.See also
updates.*
&pullRequests.grouping
config use inconsistent group-&-artifact-id matching expressions #3655