Audit GH labels

[Blacksmoke16]

GH provides native integration with some of the default labels. E.g. help wanted will call out those tickets when looking at the repos in an org for example:

Also having an actual good first issue label includes those ticket on a repo's https://github.com/athena-framework/athena/contribute page.

So, if we wanted to make use of some of those integrations we should audit our current labels to maybe adjust some of them to fit in. E.g. community:newcomer => good first issue, etc.

Originally posted by @Blacksmoke16 in #14435 (comment)

[straight-shoota]

Using standardized names makes a lot of sense to me. It helps people understand what it means and if it serves the purpose, it's just confusing to use different terms.

We would loose the community: prefix for namespacing of course, but IMO it's not that important.

[HertzDevil]

Looking at https://docs.github.com/en/issues/using-labels-and-milestones-to-track-work/managing-labels it seems good first issue is the only special label?

[Blacksmoke16]

And help wanted. Those are the only two I'm aware of.

[straight-shoota]

Okay, let's try this.

I renamed

• community:newcomer to good first issue
• community:help-wanted to help wanted

[Blacksmoke16]

Looks good, https://github.com/crystal-lang/crystal/contribute has all the good first issues, and apparently 51 issues have help wanted.