| #!/usr/bin/env bash | |
| # | |
| # This will search GitHub for hubs that use quantiles, CDF, or PMF output | |
| # types and check if they use "optional" in their hub-config/tasks.json | |
| # files. | |
| echo "======== SEARCHING GITHUB ============" | |
| curl -L \ | |
| -H "Accept: application/vnd.github+json" \ | |
| -H "Authorization: Bearer $(gh auth token)" \ | |
| -H "X-GitHub-Api-Version: 2022-11-28" \ |
Last month, I opened a discussion to formalize R package release process guidelines and it has been approved by the core devs of the Hubverse development team. The most visible change is how you will install hubverse packages. You should no longer use remotes::install_github().
To install ALL hubverse packages, you can use:
install.packages("hubverse", repos = c("https://hubverse-org.r-universe.dev", "https://cran.r-project.org"))
| #' Produce a list of all GitHub contributors to a project | |
| #' | |
| #' If you want a way to give thanks to specific people who have contributed to a project | |
| #' since a given release, this will extract the GitHub user names from a given package's | |
| #' NEWS file. This assumes that 1) the package has a `NEWS.md` file and 2) the package | |
| #' uses level 1 headers and semantic versioning for each version in the news file. | |
| #' | |
| #' @param package the name of a package | |
| #' @param since a version number (must match a version recorded in the NEWS) | |
| #' @return a character vector with GitHub user names |
| library("gh") | |
| library("base64enc") | |
| # get a file from a repository | |
| get_repo_file <- function(org = "carpentries", lesson = "sandpaper-docs", file = "CONTRIBUTING.md", ...) { | |
| gh("GET /repos/{org}/{lesson}/contents/{file}", | |
| .params = list( | |
| org = org, | |
| lesson = lesson, | |
| file = file |
| #' List maintainers who still need to respond to the Workbench transition issue | |
| #' | |
| #' @param org the name of the github organisation | |
| #' @param repo name of the repository | |
| #' @return a character vector of github user names for maintainers who still need to confirm | |
| #' transition to The Workbench | |
| #' | |
| #' @details The Workbench transition requires maintainers to confirm that they have re-cloned | |
| #' their local repositories to avoid a situation where they overwrite commits with the old | |
| #' version of the repository |
| library("jsonlite") | |
| library("polite") | |
| library("rvest") | |
| library("purrr") | |
| library("dplyr") | |
| workbench_slugs <- c( | |
| "r-ecology-lesson", | |
| "r-socialsci", |
| { | |
| "R": { | |
| "Version": "4.1.0", | |
| "Repositories": [ | |
| { | |
| "Name": "carpentries", | |
| "URL": "https://carpentries.r-universe.dev" | |
| }, | |
| { | |
| "Name": "carpentries_archive", |
I hereby claim:
To claim this, I am signing this object:
This compares the differences between pandoc's markdown and markdown_github engines when parsing <div> tags within sections.
In essence, if a <div> tag contains a header out of order with the main document, its contents will be appended to the div in the html document with markdown_github. If the following div appears after a level 3 header:
<div class='boo'>
## level 2| # test file | |
| sample_chunk <- " | |
| ```{r hello, testing=as.logical(1), another=1 + 1} | |
| x <- 1 + 1 # this evaluates to two | |
| ``` | |
| the value of x is `r x`" | |
| file = "sample.Rmd" | |
| writeLines(sample_chunk, con = file) | |
| # delete temp Rmd file | |
| on.exit(unlink(file)) |