Adding labels to issues and pull requests to tag the scope of the template involved (e.g. seven-addon) #315
Description
When I follow recent changes in the cookieplone-templates due to the lack of semantic versioning, it is difficult to check from the github listing if a PR ist e.g. just limited to – lets say – the seven addon (additional challenges apply due to trucation of the pathes in the commit logs).
If we add Labels for the template scope it would be esier to discover and filter for specific things while documentation and fine grained changelogs lack behind.
I have not yet discovered a different workflow to solve this challenge to reduce work.
Background
I was notified about a change in a PR that reads like an added SVG support is maybe relevant to backport to my exsting project. Then after reading a lot of details, it turns out it was just relevant for the seven addon template.
Keeping track of changes in cookieplone based projects is still a challenge because we have nothing in the releases area of the repo and the Changelog.md is empty and manually checking the news folder is pain.
The solution @ksuess used in this issue to add a prefix to the title works, but bloats the issue titles:
#180