Creation/Discussion on auto-labelling of PRs

[kushthedude]

Since releaseDrafter requires PR to be labelled accordingly so that they may be clubbed into a category, this issue serves as the starting of which labels and what categories should we have.

[kushthedude]

@leecalcote Let's save ourselves from the pain of maintaining a consistent PR naming or commit title. I looped upon something nice today which would do the most of work for us. We help of this little tool https://github.com/apps/probot-autolabeler, we can label PR according to changes involved concerning the directory

mesheryctl: ["/mesheryctl/"]
UI: ["ui", "/provider-ui"]
documentation: ["docs/", "readme.md", "changelog"]

and some more like the following after having a discussion .

[shivaylamba]

So Kush is it labeling the PRs based on the PR header or based on where they are made?

[shivaylamba]

Hurray First Discussions topic! Thanks @kushthedude

[kushthedude]

[shivaylamba]

Okay

[leecalcote]

This sounds really promising. Automatically assigning PR label(s) based on where changes have been made (creating a directory to label relationship) is ideal for improving our build workflow and for categorization within release notes.

[shivaylamba]

Lee I think it would be better to see it categorizing based on the task performed : bug fix, UI Enhancement, Feature and I mean based on the directory is also a great addition at the same time

[shivaylamba]

@kushthedude Is this directory reference to within the same repository?

[leecalcote]

@shivaylamba here you are - https://docs.google.com/document/d/1FzX-C_xy9hZ3Eu9dcCE0unhFV5LRUrb5YLn_MGYuG6Y/edit#. @kushthedude will be tying this off shortly and pushing out for review.