Upkeep and release to recover from CRAN's archive #11
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Render * Update .Rbuildignore * Add GitHub links to DESCRIPTION * Add URLs to DESCRIPTION * Add website on GH Pages * Style DESCRIPTION * Add package-level documentation * Add test infrastructure * Cherry-pick * Prune
…s-neitmann#4) * Render * Update .Rbuildignore * Add GitHub links to DESCRIPTION * Add URLs to DESCRIPTION * Add website on GH Pages * Style DESCRIPTION * Add package-level documentation * Add test infrastructure * Cherry-pick * Prune * Add NEWS.md * Add cran-comments.md * Add NEWS.md * Polish LICENSE * style
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Extends #10
I developed this PR as a fun project to demonstrate a modern toolkit to upkeep and release an R package to CRAN. But then why not share it and maybe help mdthemes recover from CRAN's archive :-)
usethis::use_upkeep_issue()usethis::use_release_issue().It has way too many changes for a single PR but splitting it would require some coordination and my intent is mainly to open the conversation. If you do want to use it then we can discuss how to move forward.