Running label_sync for all managed kubernetes github orgs

[Aaron Crickenberger]

Hi all,

Today, a cronjob runs label_sync against the kubernetes and kubernetes-sigs orgs [1]. This ensures the same set of labels exist across all repos [2].

I'd like to update the job to run against the remaining actively managed kubernetes orgs: kubernetes-client, kubernetes-csi, and kubernetes-incubator

Lazy consensus: if I hear no objections here or in the PR [3] by Monday 3pm PT, I will proceed.

- aaron

[1] https://github.com/kubernetes/test-infra/blob/master/label_sync/cluster/label_sync_cron_job.yaml#L35

[2] https://go.k8s.io/github-labels

[3] https://github.com/kubernetes/test-infra/pull/9054

[Morgan Bauer]

I think this is a positive for consistency. Especially for new projects.

How much of each label is synced? Is it only the label-text? Do we also get the description and colors?

--
You received this message because you are subscribed to the Google Groups "Kubernetes developer/contributor discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-de...@googlegroups.com.
To post to this group, send email to kuberne...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/05c53ad5-516e-4a3a-ace8-5154acbaa890%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Aaron Crickenberger]

Everything gets synced.  Description, colors, migration of other labels.  The sight of bland, colorless labels in kubernetes-csi repos using prow may have had something to do with my decision to kick this off :)

Also, the sync is additive.  If your repo has labels not mentioned in label_sync's config, they will be untouched.

- aaron

[Aaron Crickenberger]

Having heard no objections, the PR has merged.  Changes will take effect the next time label_sync runs.

- aaron