Feature request: Generate tags on PRs based on changesets

[timleslie]

For my project we have a convention of listing the packages being touched in a PR in the title, so the pull request page will look something like:

• package-A: Add new feature
• package-B,package-C: Fix some bugs
• pkg-D: Do some work

This is an error prone, inconsistent, non-filterable system. It occurs to me that we could be using tags rather than coding this info in the PR title. If we're going to do that, then we could take advantage of the changeset-bot to do this automatically for us. It will be able to give us more consistent data and will also make it obvious at a glance what kinds of changes are in the PR pipeline.

The tags would probably be something like package-name - major for e.g.

This tagging solution might not be appropriate for all users of the changeset bot, so it would probably make sense for it to be an option feature which can be switched on/off.

[Noviny]

I'm a bit hesitant to use github tags for something like this, as it seems like it would make tags be quite loud.

Quick q: When does this information get referenced? Just in the PR, or does it get referenced ✨ the future ✨ as well?