-
Notifications
You must be signed in to change notification settings - Fork 423
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
Having difficulty creating my globs #801
Comments
Hello @LimesKey |
I m also facing this issue, Looks the the exclusion is not working as expected.
In this case the label should not be added if the changed file is present in But the label is being added for any change. |
@sameershelar-paypay, you're missing the top-level |
I am having similar issues with the exclusion not working.
Shouldn't one use |
@HarithaVattikuti Is there any update on this? I've used the exclusion as demonstrated in the example section but it does not work. |
Hi @LimesKey , We did work on your request from the provided details we would suggest to pass a comma seperated list of globs for Dev and Invalid invdividually to achieve desired result. Dev and Submission label wont come together as they are reverse of each other, but same cannot be said for Dev and Invalid because the conditions mentioned for the Invalid covers all the cases for Dev label which basically makes Dev a subset of Invalid. |
Thanks. Could you provide an example of a working list? As I see it, the syntax used by @LimesKey is like suggested in the README, except that he uses
|
Sorry, not a bug report, I just couldn't find another place to post this.
I'm hoping to issue 3 labels to pull requests for my repo, one for 'Submission', 'Dev' and 'Invalid'. Having a little trouble understanding how to create globs, I've asked ChatGPT several times but I seem to be getting back code with syntax errors and nothing like what's in the README.
Submission
The Submission label should be applied if there are changes to the
/projects
directory but NOT if there are changes in other top-level directories and or in their subfolders, other than/projects
of course.Dev
This should almost be the reverse of 'Submission', which should apply when there are changes to any root directories and their subfolders but NOT when there are changes to the folder or any subfolders in the
/projects
directory.Invalid
This should apply if there are changes in
/projects
AND in any other top-level directories (other than /projects) and their subdirectories.Here's my current
labeler.yml
Currently, when there are changed files in the top level directory and in the
/projects
folder theDev
andInvalid
label apply when theInvalid
label should only be applied. TheDev
andInvalid
label should never be applied at the same time.The text was updated successfully, but these errors were encountered: