Create auto labeler workflow for PRs [skip ci]

[mshima]

Following #11283

This PR creates a workflow for auto labeling PRs based on the files changes.

It uses scheduled runs and tags PRs that aren't tagged yet.
Why don't use on pull_request? actions/labeler#12
Once this bug is resolved, we should switch to on pull_request.

• Please make sure the below checklist is followed for Pull Requests.

• All continuous integration tests are green

• Tests are added where necessary

• Documentation is added/updated where necessary

• Coding Rules & Commit Guidelines as per our CONTRIBUTING.md document are followed

[pascalgrimaud]

why is it your own action ? did you fork the project ? in this case, we can host it under jhipster organization

[mshima]

Sure.
The changes I’ve made is actions/labeler#49.
I don’t have permission to create new repositories.
Can you clone my?
If you clone upstream, then you have to copy the dependencies too.

[pascalgrimaud]

I'm afraid of this, as it will be launched all the time and we won't find in Actions list the other builds

[mshima]

We can reduce this to one an hour.
I’ve set to 5 min to test.

[SudharakaP]

I am a bit doubtful on this change. Maybe we need to think of a different approach 🤔

1. I think this action only adds labels and it doesn't remove them. Say I make a commit changing package.json and then in a later commit removes those changes. Then the label theme: dependencies might be staying; there's an issue for this in the parent repository; Remove labels for reverted changes actions/labeler#14

2. Since the action is forked from https://github.com/actions/labeler and there's some customizations and we'll have to maintain it and probably merge upstream enhancements (such as the useful Remove labels for reverted changes actions/labeler#14) when they are available.

Just my two cents 😄

[mshima]

I am a bit doubtful on this change. Maybe we need to think of a different approach 🤔

1. I think this action only adds labels and it doesn't remove them. Say I make a commit changing package.json and then in a later commit removes those changes. Then the label theme: dependencies might be staying; there's an issue for this in the parent repository; actions/labeler#14
2. Since the action is forked from https://github.com/actions/labeler and there's some customizations and we'll have to maintain it and probably merge upstream enhancements (such as the useful actions/labeler#14) when they are available.

Just my two cents 😄

I think labeling removing is minor.
Another problem is that it don’t revisit a modified PR to add new labels.
But it a start. We have a lot of unlabeled PRs.

Another approach is to create jhipster teams and use code owner.
It will ask the team to review the PR based on code owner.

[CLAassistant]

All committers have signed the CLA.