Skip to content

Label Conversion Tracker #1562

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Azaya89 opened this issue May 9, 2025 · 7 comments
Closed

Label Conversion Tracker #1562

Azaya89 opened this issue May 9, 2025 · 7 comments
Assignees

Comments

@Azaya89
Copy link
Collaborator

Azaya89 commented May 9, 2025

Label Conversion Tracker

This checklist helps track conversion of legacy type: labels to GitHub's native issue types or Discussions.
This is part of the proposal to standardize labels raised in holoviz/holoviz#430

type: bug → Bug

Found 78 open issues.

type: enhancement → Enhancement

Found 83 open issues.

type: docs → Documentation

Found 75 open issues.

type: discussion → Discussions

Found 23 open issues.

@Azaya89 Azaya89 self-assigned this May 9, 2025
@maximlt
Copy link
Member

maximlt commented May 9, 2025

How about issues that have multiple status tags? This one for example #531 (picked randomly).

@Azaya89
Copy link
Collaborator Author

Azaya89 commented May 11, 2025

How about issues that have multiple status tags? This one for example #531 (picked randomly).

I would have to select one then based on the most relevant. In this example, it can be converted to a Discussion with an enhancement label attached to it.

@Azaya89
Copy link
Collaborator Author

Azaya89 commented May 11, 2025

FYI: Here’s a screenshot of the progress made before the tracking checklist was overwritten on update. I noticed GH Issues only lists up to 30 Issues by default, so I had to update the limit.

These issues had already been converted and checked off but are no longer listed here because they don’t match the label query anymore.

Image

Anybody can feel free to tick off some of the listed Issues as well :)

@maximlt
Copy link
Member

maximlt commented May 12, 2025

I'm not sure I understand what is going on here :) Are you listing all the hvPlot issues in this issue? Is that to track how they're manually converted from using GH labels to GH issue types? If so, this is not the idea I had in mind, which was to come up with a script we could develop and improve while applying it to hvPlot's repo, script that would then be useful for the other HoloViz repos.

I would have to select one then based on the most relevant. In this example, it can be converted to a Discussion with an enhancement label attached to it.

For example, I would expect the script not to migrate issues that have multiple type labels. Instead, the script should create a file that contains a link to each one of them, so that someone can then manually go through each one of them.

I noticed GH Issues only lists up to 30 Issues by default, so I had to update the limit.

What limit did you increase exactly?

@Azaya89
Copy link
Collaborator Author

Azaya89 commented May 12, 2025

I wrote a GitHub CLI script that finds all open Issues with the label "Type:<bug/docs/enhancement/discussion>" and lists them here with their links. The lists are grouped by Label type and then I manually convert them to the appropriate Issue Type and tick it off as done. This script can be applied to any of the Holoviz repos.

The initial script only listed the first 30 Issues (GH Default), so I had to modify the script and increase the limit that can be allowed per label category.

Github does not currently have a way to automatically assign Issue Types so it has to be done manually. This Issue is a way to track my progress as I go through the Issues one by one :)

@maximlt
Copy link
Member

maximlt commented May 12, 2025

Github does not currently have a way to automatically assign Issue Types so it has to be done manually.

Hm this seems to imply it's possible https://github.blog/changelog/2025-03-18-github-issues-projects-rest-api-support-for-issue-types/

If not possible, please don't go any further, as converting hundreds of issues manually (and thousands for the other repos) is not worth the trouble imho.

@Azaya89
Copy link
Collaborator Author

Azaya89 commented May 15, 2025

I think this is resolved now.

@Azaya89 Azaya89 closed this as completed May 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants