Should we add an autolabeler for PR?

[mofosyne]

https://github.com/actions/labeler

This would possibly allow use to apply general labels based on what files was changed in the PR. E.g. these are the categories we should identify

• documentation only changes
• main program UI changes
• backend logic changes
• python tooling changes

etc... identifying the language and level of complexity (via file/folder) could also be helpful as different people have different capabilities and showing what files was changed and expected expertise level could help with directing attention to what PR is easy or harder to deal with.

[ggerganov]

I not familiar with this, but I'm curious to give a try and see if it would be useful

[mofosyne]

I'll add myself to assignee if I decide to tackle this, but for now anyone else is invited to give this a shot (just remember to claim it here)