search

tidyverse / tidyversedashboard

Tidyverse activity dashboard
https://tidyverse.org/dashboard
Other
72 stars 24 forks source link

In repo summary, use labels as present in the repositories? #7

Open maelle opened 6 years ago

maelle commented 6 years ago

Again, not sure if generally useful and something I did for Locke Data package repos where "bug" is not a label.

I used the labels present in the repositories for the repo summary https://github.com/lockedata/tidyversedashboard/blob/master/R/repository.R#L54

I also wonder whether labels should be merged when they're not homogeneous. E.g. the repo summary says there's 0 bug for dplyr because there the bugs are "bug 💣 ", but having two columns "bug" and "bug :bomb: " might not be very handy. Maybe num_label should use a regexp.

Sorry this was a messy issue!

maelle commented 6 years ago

Using all labels in the summary is probably not a good idea 🤔 but using a regexp maybe a better one 😁

jimhester commented 6 years ago

Yeah, maybe this should just be a parameter to the report of what labels to aggregate by. It could just be a named list if there are ones you need to map to a common category, e.g.

issue_categories <- c("bug 💣" = "bug", "bug" = "bug", "feature" = "feature")