Add `major`, `minor`, and `patch` labels to PRs, Issues

[kenperkins]

I think it would be nice to be able to label (and filter) PRs & issues, and to have some insight before even reviewing changes as to how they impact SemVer. There are a lot of issues and PRs that have already been submitted and there's little context to them on real or potential impact to SemVer.

I opened this in part to help to understand impact of an issue, say #66, which I assume to be major at such time as they're actually removed.

[indutny]

Good idea, +1

[brendanashworth]

This would be a good addition and make it easier for a new contributor to help out. 👍

[nelsonpecora]

👍 I think that would be helpful for maintainers, contributors, and users (who watch PRs that they want/need)

[nelsonpecora]

I am not good at interacting with robots. Glad this is getting some traction, though!

[piscisaureus]

+1 from me too.

As possible refinement, we could tag issues "bug fix", "api change" and "api addition". I think that's more clear for people who aren't thinking about semver all day long.

[kenperkins]

@piscisaureus a risk of not being explicit with semver-matching labels is someone making a mistake and not realizing that there is an implicit meaning. For example, api-change doesn't always mean breaking.

[nelsonpecora]

Yeah, I'm wary of using non-semver terminology. major means that there's an api change, and that api change is breaking. It's much more defined and explicit.