-
Notifications
You must be signed in to change notification settings - Fork 8
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
automatically parse R package versions #13
Comments
or maybe even with curl R and the R interface of jq, https://docs.ropensci.org/jqr/ |
Hi Philip, thanks for the suggestions. Our current manual is always knitted manually and pushed to this repository, and then GitHub actions release the version online. I never worked with such auto-pulling of information, so I wonder if this operation you suggested can be placed together within the GitHub actions or some auto-knit function. Would you happen to know how to do this? |
Hi @zecojls sorry I am a bit late with responding because of traveling. Yeah, good question how to technically implement it. I think some GitHub actions to set up pure jq or its R interface would be a good enhancement. Have you thought about using quarto? As far as I can tell, this could also be set up with GH actions. |
@zecojls shall I draft something, i.e., making a PR for this feature? |
Hi Philipp, I would greatly appreciate it if you start drafting something. |
Hi, I would suggest to use some automated way to parse R package versions. For opusreader2, for example, something along the line of
could be used, and afterwards some
jq
CLI based filtering in the pipe would be useful to extract versions on the current master build as deployed on r-universe. Regarding CRAN, we plan to release a first version roughly in June 2023 (meaning then a DESCRIPTION filter can be used for official purposes).Cheers,
Philipp
The text was updated successfully, but these errors were encountered: