We could add the pull request labeler an action for automatically labelling pull requests

[jbampton]

The main reasons for adding the actions/labeler are:

• Consistency in Labeling
• Increased Productivity and Efficiency
• Improved Organization and Discoverability
• Enhanced Collaboration
• Automation of Workflows
• Scalability and Maintainability

https://github.com/actions/labeler

[dave2wave]

We should discuss what types of labels to generate.

1. Documentation on any *.md changes.
2. Source on any *.py changes.
3. Static on any static/** changes.
4. Templates on any templates/** changes.
5. Workflows on any .github/** changes.

@sbp anything else?

[sbp]

I'd add:

1. Routes for any atr/{get,post,shared}/** changes.
2. Storage for any atr/storage/** changes.
3. Tests for any playwright/** or tests/** changes.
4. Migrations for any migrations/** changes.
5. Containers for any Dockerfile.alpine, Dockerfile.ubuntu, or start-atr.sh changes.

And possibly consider Tasks for atr/tasks/**, Models for atr/models/**, and Scripts for scripts/**. Of those three I'd say that Models are most important.