-
-
Notifications
You must be signed in to change notification settings - Fork 111
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
Comments
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 |
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. Anybody can feel free to tick off some of the listed Issues as well :) |
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.
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.
What limit did you increase exactly? |
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 :) |
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. |
I think this is resolved now. |
Uh oh!
There was an error while loading. Please reload this page.
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
→ BugFound 78 open issues.
cmap
option ignored in a line plothist
only support numerical or datetime fieldsgeodataframe.hvplot.paths(geo=True)
, the Polygon is not enclosed in the resulting Bokeh plotc
color parameter of a scatter plotValueError: cannot convert float NaN to integer
with the air datasettype: enhancement
→ EnhancementFound 83 open issues.
hover_tooltips
,hover_formatters
,hover_mode
added in HoloViews 1.19import hvplot
by lazily loading dependencieshvplot
levelpandas.Interval
arrays instep
plotsgroup
argument tohvplot()
callsdatashade=True
andc
to the scatter matrix plothvplot.scatter_matrix
?yaml()
methodtype: docs
→ DocumentationFound 75 open issues.
'y'
argument ends up being 'x' label - rename it tocolumns
?opts
should be mentioned in hvplot customization reference pagerasterize=True
together withby
clim_percentile
hvplot.help
widgets
orwidget_location
changes return type from holoviews to panelvalue_label
is not documenteddecimate
operationpersist
type: discussion
→ DiscussionsFound 23 open issues.
The text was updated successfully, but these errors were encountered: