Skip to content

Expand the filter-pattern compliance corpus against real GitHub runs #8

Description

@Co-Messi

Body:

The filter-pattern engine is the highest-fidelity part of actwhy, and the compliance corpus is how we keep it honest. We want more cases — especially the ones naive matchers get wrong.

High-value additions:

  • ? (zero or one of the preceding character) and + (one or more of the preceding character) — confirm they are not treated as wildcards.
  • ! negation ordering, where a later negation overrides an earlier match.
  • Character classes […] combined with * / **.
  • tags versus branches behavior with /-containing patterns.

For each case, cite the source: GitHub's filter-pattern docs, or a real run you reproduced. See CONTRIBUTING.md.


Activity

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

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions