Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Ability to filter with label wildcards?
See original GitHub issueWe 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?
Issue Analytics
- State:
- Created a year ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I think we’d definitely accept regex / glob matching prs