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
Add git tagging to devtools::release() #1198
Comments
One problem is that, right after you run release(), you can't be sure that the submitted package will actually be accepted onto CRAN without any revisions. |
Or that Brian Ripley won't give you two weeks to upload a revision, after it's been published, to fix a single non-ASCII character in an .Rd file! In practice the revisions that @wch refers to happen all the time immediately after first submission. |
Just another thought about this: One thing that Seeing the file there would serve as a reminder to tag the commit before committing more code. |
Oh I like that idea! |
This old issue has been automatically locked. If you believe you have found a related problem, please file a new issue (with reprex) and link to this issue. https://reprex.tidyverse.org/ |
Many R packages, including those in rOpenSci use git tags/github releases to identify their CRAN releases, and include updates from the NEWS file in the GitHub release info.
Could this be automated as part of devtools::release()?
(cc @scottkosty, @njtierney, @kbenoit)
The text was updated successfully, but these errors were encountered: