-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Label filters based on Head & Base branch names #27
Comments
Hello @deepakputhraya, I appreciate your idea. Could you be so kind and specify what you mean with the |
Apologies not being explicit. I just assumed the AND case with
I would like to make a small correction
Ignore branches with specific names for this rule. This is probably possible to support with regex but the thought here was to make the rule more readable. Do you think adding filter like PR size to this make sense? I understand that there are Github actions for this specific scenario, but providing PR size filter with base & head would make it more customizable.
Assuming that it is AND across properties and OR within a property. |
To be honest, in my opinion the I agree that an optional
same as
What is your opinion @TimonVS ? |
As long as we have sane default values or ignore fields that are not set it would still remain simple. Options such as |
@deepakputhraya feel free to fork and do a pull request :) |
Hey @deepakputhraya! Those are some good suggestions. I feel like we can add I'm not entirely convinced that we should add the Would you have time to work on this feature? |
I would really be interested by a way to automatically add a label based on the target branch. For instance, I'd like to add automatically an Did you tried somethihng @deepakputhraya ? |
Hello, I created a PR for it ➡️ #61 It only adds the |
Any chance to get the above PR reviewed/released? It would definitely help us! |
Are there any plans to add labels based on regex matching head/base branch?
Current config -
Suggested config
This could give more control over labelling.
The text was updated successfully, but these errors were encountered: