When running
create_github_labels(label_csv = "../Downloads/github_labels.csv", owner = "DC23", repo = "DC23/workflow-tests", delete_previous = TRUE)
I get
Parsed with column specification: cols( print_order = col_double(), type = col_character(), label = col_character(), color = col_character(), use_prefix = col_logical(), description = col_character(), long_description = col_character() ) Error in gh::gh(cmd, owner = owner, repo = repo, name = label, color = color, : GitHub API error (404): 404 Not Found Not Found

While it is possible that the GitHub API has changed, I can't rule out whether this is because I am passing bad arguments to owner or repo.

Note my GitHub access token is fine.

Related to the next round of releases after #26: If issues.R included this GitHub default label, the release checklist would get hyperlinked on the Software/Data/Library Carpentrie' repo list.

I'm not entirely sure whether labels are implicitely supported by gh, since a the ... parameter is present, I guess they can be inserted and processed.

not that this project will ever be published on CRAN, but there is already a carpenter package apparently: cran.r-project.org/package=carpenter

https://github.com/fmichonneau/carpenter/blob/92349a2aecb7ab922cce0a8c741e30bcf4fd3380/R/github_labels.R#L112

https://github.com/fmichonneau/carpenter/blob/92349a2aecb7ab922cce0a8c741e30bcf4fd3380/R/github_labels.R#L144-L154

This looks to me like existing labels will be deleted without replacement, not mapped to the handbook's set. Is that true?

Because that would delete labels from the issues & PRs that the maintainers have labelled so far.

cc @tracykteal & related to carpentries/docs.carpentries.org#134