Issue of the label configuration file ".github/labeler.yml" about labeler HOT 11 CLOSED

Ok, I have found what is the culprit there. The meaning of any and all is poorly defined. The issue there is that

- any: ['./*', './src/*']

and

- ./*
- ./src/*

Have different meaning. The list in any mean that any file in the PR must match all globs in the list. With all it mean that all files in the PR must match all globs in the list. So to have the same behaviour with any you need to use:

- any: ['./*']
- any: ['./src/*']

from labeler.

Hello everyone!
We have released a new major version of the action. The behaviour of the any selector was changed to match ANY file against ANY glob pattern so it became more intuitive. Please find more details in the release notes.

Could you please use the new version and provide us with your feedback?

from labeler.

I also spotted this. It happens if I have more than one entry in the any specifier.

from labeler.

Have different meaning. The list in any mean that any file in the PR must match all globs in the list. With all it mean that all files in the PR must match all globs in the list. So to have the same behaviour with any you need to use.

Nope. Still don't get it 😅

from labeler.

@mittalyashu assume that you have such definition any: ['src/*', '*/test/*']. Then it will apply the tag if any of the files matches all globs. So for example if your PR changes files:

• examples/foo
• src/test/foo

Then it will apply, as src/test/foo matches both of the globs. However if list of files would look like:

• examples/test/foo

Then it will not match, because while */test/* matches, the src/* doesn't, so whole filter fails.

You can think of it like (using Ruby syntax):

• any - changed_files.any? { |file| matches.all? { |match| file.matches(match) } }
• all - changed_files.all? { |file| matches.all? { |match| file.matches(match) } }

from labeler.

Oh! I see.

Well, seems like the docs were not clear.

I was thinking that in the any filter, it will match any globs listed in the array.

In that case, doesn't that means any and all both plays the same role?

from labeler.

Not quite. all will check if all modified paths matches while any will check if any modified patch matches.

from labeler.

Another user has the similar problem:
https://github.community/t/labler-action-error-typeerror-glob-pattern-string-required-glob-pattern-string-required/140738

He gets the same error message:

##[error]TypeError: glob pattern string required
##[error]glob pattern string required

from labeler.

Hi team,

Could anyone take a look at this issue?

from labeler.

I'm also running into this issue. I'm unable to use any configuration that has any in it on 2.2.0.

from labeler.

Hit this error just now:

• https://github.com/OpenISS/OpenISS/blob/master/.github/labeler.yml
• OpenISS/OpenISS#86
• https://github.com/OpenISS/OpenISS/runs/4811417470

It appears to have labeled two things correctly before barfing out.

from labeler.