Ability to filter with label wildcards?

[petemounce]

We use a hierarchical labelling system where I am. For example, origin/customer/{name-of-customer}, area/product/widget-factory/windows.

I'd really like to have closer control over how to route issues, so that I could, for example, do label: area/product/* and add that to the product-manager triage project, vs area/internal/foo to a different project.

We have quite deep hierarchies; being able to use glob semantics (? for wildcard single character; * for wildcard between /, and; ** for recursively wildcard) would be extremely useful.

Is that something you would support, either by implementing directly, or by accepting an appropriate-quality-standards PR?

[skw]

:wave: Hi @petemounce this seems like a really useful improvement. Contributions are generally welcome but I'll defer to @mattcosta7 who's been owning this action 🙇

[mattcosta7]

I think we'd definitely accept regex / glob matching prs

[austenstone]

Here's some sudo code to condition on the labels with regex using actions/github-script

- uses: actions/github-script@v6
  id: my-script
  with:
    script: return context.issue.labels.reduce((p,c) => p ? p : c.match(/regex here/g), false)
- run: echo "OK"
  if: steps.my-script.outputs.result

[petemounce]

Thanks for the prior art! I'd prefer to just glob, for the simpler UX. What do others think?

[mervyd]

#182