syncing labels for projects is cumbersome and error prone

[jtnord]

Service(s)

GitHub

Summary

Today it is cumbersome to sync a repositories labels to the the expected use cases configured in the organisation release drafter.

Not only do you have to create the labels, but ensuring the colour is consistent across all repositories is a PITA.

as per https://groups.google.com/g/jenkinsci-dev/c/A54eSh0ueSA/m/mHSASibjCQAJ filing this (its not an issue but an RFE).

Reproduction steps

1. have a repo in the jenkins org
2. setup all the labels for release drafter in the consistent colours
3. notice how repetitive this is across many repositories when CD enabling / incrementality them is

[lemeurherve]

Related, script to create default labels: jenkins-infra/jenkins.io#6699

[timja]

I'm assuming default labels don't work on forks?
https://github.com/organizations/jenkinsci/settings/repository-defaults (requires org owner)

Another approach would be to change hosting to create a repo and push the code and then rely on our configured defaults

cc @NotMyFault

[NotMyFault]

I'm assuming default labels don't work on forks?
github.com/organizations/jenkinsci/settings/repository-defaults (requires org owner)

I created the labels yesterday to be an exhaustive list, but I don't think it'll apply to forks, given

Set the labels that will be included when a new repository is created in this organization

[timja]

I created the labels yesterday to be an exhaustive list, but I don't think it'll apply to forks, given

I just tested it and it does:
https://github.com/jenkinsci/label-test/labels

(delete the repo when you're done looking)