Skip to content

feat: support negation globs in config.yaml#3156

Open
btrautmann wants to merge 6 commits intomobile-dev-inc:mainfrom
btrautmann:bt/feat/negation-globs
Open

feat: support negation globs in config.yaml#3156
btrautmann wants to merge 6 commits intomobile-dev-inc:mainfrom
btrautmann:bt/feat/negation-globs

Conversation

@btrautmann
Copy link
Copy Markdown

Proposed changes

Adds support for negation globs in config.yaml to support excluding specific globs before Maestro processes them as flows. This is helpful when you have other .yaml (similar to config.yaml) files in our workspace but don't want them to be treated as flows, as it avoids needing to either restructure your project (add a nested directory for your workspace) or writing custom code to generate a config.yaml without the excluded file at test time.

copilot:summary

Testing

Added fixtures and tests to exercise the new logic.

Does this need e2e tests? Please consider contributing them to the demo app repository.

btrautmann and others added 2 commits April 9, 2026 13:33
Upstream added 018_additional_config_files in mobile-dev-inc#3150, conflicting with our
018_negation_with_specific_positive fixture. Renumbered ours to 019.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Extract duplicated matcher-building logic into a local buildMatchers function
- Fix error message to only list positive globs under "inclusion pattern(s) did
  not match", excluding !-prefixed negation patterns which are not inclusions

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@btrautmann btrautmann requested a review from proksh April 9, 2026 17:36
Copy link
Copy Markdown
Contributor

@proksh proksh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice.

It will be good if you can test "all negation, no positive" case for flow selection as well.

@Fishbowler
Copy link
Copy Markdown
Contributor

What's the expected outcome? Zero flows?

@proksh
Copy link
Copy Markdown
Contributor

proksh commented Apr 9, 2026

What's the expected outcome? Zero flows?

I was thinking just excluding the mentioned exclusions and running all remaining flows. But you have more context of how things should work, and if Zero flows make more sense, lets go with it.

@btrautmann
Copy link
Copy Markdown
Author

@Fishbowler @proksh lmk if you'd like me to make any further changes, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants