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
{{ message }}
This repository has been archived by the owner on Jun 25, 2024. It is now read-only.
For now is it enough to add 2 entries for the one that is not working?
Absolutely. ^^
I think only less common glob patterns like exclusions (e.g. [!asdf]) would not have an easy workaround, but those aren't very useful for path matching here anyway.
No rush on this, it was just unexpected that glob patterns only work if * is included too. Thanks!
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
Only
*
and**
work when used in a path trigger. It would be nice to use curly braces too.Curly brace patterns are supported by
doublestar
(the library used for*
/**
in this repo), and actually work currently, but only if thepath
includes*
too.Example
Suggestion
I believe this is the relevant code? Maybe it's sufficient to check for pairs of brackets too?
This is probably a breaking change, since existing path triggers containing brackets
{}
/[]
might behave differently (if those paths don't contain*
).https://github.com/monebag/monorepo-diff-buildkite-plugin/blob/3f65d099261bf9680da137cc4cabc363bcabcb8d/pipeline.go#L120-L125
The text was updated successfully, but these errors were encountered: