[FEATURE] template-oss should manage labels

[wraithgar]

trafficstars

The settings.yml file inheritance model does not work. We should let template-oss manage labels, if that's at all possible.

We may end up in a situation like the current one, where inheritance doesn't work. It would mean template-oss itself needs to build the settings file from its template any any optional additional file that we allow for in each repo.

[lukekarrys]

For reference here is the list of labels from the wiki which might be outdated by now.

Something to keep in mind for this feature is that it should allow config if we want to apply it to the cli (such as not deleting untracked labels).

Types

Label	Description
	things that need fixing
	further information is requested
	this change only modifies documentation
	a larger scope of work that will be tracked in a Project Board
	a "backlogged" item that will be tracked in a Project Board
	will be discussed at the Open RFC call
	meeting agendas
	new feature or request
	good issue or PR for newcomers
	another pull request or issues already addresses this
	this will not be worked on
	specific to registry implementation
	specific to website implementation
	specific to security implementation
	this RFC is ready for implementation
	Help Wanted: extra attention is needed
	not ready to merge yet
	is pending a discussion
	requires tests before merging
	pull request requires docs before merging
	pull request is for a specific npm release
	backwards-incompatible breaking changes
	new backwards-compatible feature
	semver patch level for changes

[nlf]

Here's the labels we want (we think)

Label	Color	Description
	#00cc00	Dependency updates
	#1664ff	Issue awaiting triage
	#ededed	Needs more info to continue, like a reproduction
	#e54572	Highest priority
	#ba20ab	Second highest priority
	#412379	Third highest priority
	#000000	Not a current priority
	#d0021b	Security related issues

[wraithgar]

the autorelease tags that release-please uses are definitely needed

[lukekarrys]

here are all the labels in all of our repos, sorted by how many repos have that label. note this doesn't say anything about how many issues/prs have that label, but just gives us a baseline to not accidentally clobber anything important.

Label	Color	Repo Count
	#00cc00	73
	#ededed	67
	#ededed	66
	#F5A623	56
	#0E8A16	55
	#1D76DB	55
	#D93F0B	55
	#D0021B	55
	#D0021B	55
	#000000	54
	#105DE0	54
	#D0021B	54
	#D0021B	54
	#1664ff	54
	#fbca04	54
	#BA20AB	54
	#412379	54
	#E54572	54
	#1d76db	53
	#fef2c0	53
	#D0021B	53
	#0E8A16	48
	#0E8A16	48
	#E31919	42
	#000000	39
	#000000	39
	#ededed	38
	#80C000	20
	#DDDDDD	19
	#FF8000	18
	#FFC000	18
	#4080FF	18
	#C080FF	18
	#00C0FF	18
	#C00000	18
	#DDDDDD	18
	#000000	4
	#F7FE11	3
	#F8E71C	3
	#ededed	2
	#313DB0	2
	#ededed	2
	#ededed	2
	#000000	2
	#000000	2
	#7CF1B9	2
	#B6476B	1
	#F9C321	1
	#c2e0c6	1
	#D4C5F9	1
	#D4C5F9	1
	#D4C5F9	1
	#F9D0C4	1
	#F9D0C4	1
	#FEF2C0	1
	#FEF2C0	1
	#F9D0C4	1
	#F9D0C4	1
	#FEF2C0	1
	#F9D0C4	1
	#D4C5F9	1
	#D4C5F9	1
	#D4C5F9	1
	#D4C5F9	1
	#D4C5F9	1
	#D4C5F9	1
	#D4C5F9	1
	#D4C5F9	1
	#F9D0C4	1
	#F9D0C4	1
	#FEF2C0	1
	#D4C5F9	1
	#F9D0C4	1
	#000000	1
	#FEF2C0	1
	#F9D0C4	1
	#fef2c0	1
	#F9D0C4	1
	#F9D0C4	1
	#fbca04	1
	#FEF2C0	1
	#FEF2C0	1
	#1d76db	1
	#260531	1
	#FEF2C0	1
	#F9D0C4	1
	#E728D1	1
	#4C76B6	1
	#242697	1
	#DC2FBF	1
	#7AEB62	1
	#42F9C7	1
	#1A29C5	1
	#596642	1
	#705E93	1
	#B8F041	1
	#D04CB9	1
	#ededed	1
	#000000	1
	#D0021B	1
	#D0021B	1
	#343DFF	1
	#E3AF50	1
	#D0021B	1
	#000000	1
	#1d76db	1
	#fbca04	1
	#1d76db	1

[nlf]

here's the list of labels that i was going to propose for the probot settings app

labels:

• name: Agenda color: "#F5A623" description: Will be discussed in an Open RFC call
• name: Bug color: "#E31919" description: Issues where an existing feature is not working as intended
• name: Dependencies color: "#00CC00" description: Dependency update pull requests
• name: Enhancement color: "#0E8A16" description: Request for a new feature or improvement to an existing feature
• name: Good First Issue color: "#0E8A16" description: Issues that are ideal for a new contributor to work on
• name: Needs Discussion color: "#D0021B" description: Issues that need further discussion before prioritizing or accepting
• name: Needs Documentation color: "#D0021B" description: Pull requests that need documentation added before merging
• name: Needs Tests color: "#D0021B" description: Pull requests that need tests added before merging
• name: Needs Triage color: "#1664FF" description: Issues that need to be triaged by the npm team
• name: Priority 0 color: "#E54572" description: Immediate priority
• name: Priority 1 color: "#BA20AB" description: High priority
• name: Priority 2 color: "#412379" description: Low priority
• name: Backlog color: "#000000" description: Lowest priority
• name: Security color: "#D0021B" description: Security related issues and pull requests
• name: "autorelease: pending" color: "#EDEDED" description: Pull requests for releases that have not yet been published (used by bots only)
• name: "autorelease: tagged" color: "#45B4D6" description: Pull requests for releases that have been published (used by bots only)