Add support for regex path based selection #269
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Use case: We were trying to configure a set of pipelines that are sometimes working in the top level of the code base and sometimes not. We are using
set_pipelineand a template pipeline in Concourse to configure these.Because neither
""(matches nothing)"*"(only matches top level directory changes) match we are unable to match the entire fs tree of the PR. This causes certain builds to not trigger. I've updated the documentation forpathsto reflect that this isn't using glob syntax and is usingpath/filepath.MatchsyntaxThis change adds support for identifying paths using regexes. This solves our use case by allowing us to use
^.for anything in the top level andpath/to/subproject/^.for anything else.