chore: update labels.json

[moul]

Based on https://github.com/golang/go/labels?page=2&sort=name-asc

Depends on gnoverse/gh-labels#127

Need help for colors.

Checklists...

Contributors Checklist

• Added new tests, or not needed, or not feasible
• Provided an example (e.g. screenshot) to aid review or the PR is self-explanatory
• Updated the official documentation or not needed
• No breaking changes were made, or a BREAKING CHANGE: xxx message was included in the description
• Added references to related issues and PRs
• Provided any useful hints for running manual tests
• Added new benchmarks to generated graphs, if any. More info here.

Addresses gnolang/meetings#18

[moul]

@zivkovicmilos what will happen once merged, because I see that we’ve some labels that are not defined by this file, i.e., labels used by the labeler.yml.

[zivkovicmilos]

@moul
Actually nothing will happen, unless we run the GitHub label-er tool on the repo (currently private).
It's not dynamic in a sense that it triggers GitHub labels to change, the tool needs to be manually run using the labels.json file

[moul]

OK, and do you think that running it can actually delete labels from labeler.yml?

Would you mind reviewing my PR and running the script yourself?

[zivkovicmilos]

OK, and do you think that running it can actually delete labels from labeler.yml?

Would you mind reviewing my PR and running the script yourself?

I just checked the labels we have in the labels.json and the labels we have defined in the repo.
I can confirm that running the label tool with this json file will delete labels that are not defined in the labels.json, but are defined in the repo. To avoid this, we just need to make sure the labels.json contains all up-to-date labels we added manually since last running the tool.

The tool assumes that the labels.json is the source of truth, so in reality we should only be updating this file, and run the tool afterwards

Do you want me to push to this branch the changes that are needed to make sure we preserve everything?
You'd need to run the tool yourself after those changes, because I don't have repo modification permissions

[moul]

Can we update the tool so it can also fetch the current list, so we can fetch the list, make changes and then publish; otherwise we need to manually review the difference and expect no typo/utf-8 issues.

Then, once the tool support fetching, we can run it and update some guidelines to make it the new way of managing labels in the future.

---

Edit: I've tasked @gnolang/devrels with delving deeper into this matter, encompassing both the current situation and the wider context. The objective is to establish a cohesive strategy for label management. Perhaps centralizing the process through an organization-wide repository, as opposed to individual .github/ folders, might be more effective. Additionally, we should ensure that any new labels introduced by someone or an automated process are preserved and not inadvertently removed.

[moul]

Assigning this to @gnolang/devrels for follow-up.
Please, be careful not to delete labels to avoid manual relabeling of issues.
I highly recommend working on a fork before making these changes.
Thank you.