-
Notifications
You must be signed in to change notification settings - Fork 289
Reduce number of manual git release steps #1746
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm pretty ambivalent about these changes, as it feels like I'm going to be faced with choices like "shall we do X and Y?" and I might only want to X but I can't do X until or unless I want to do X and Y at the same time. I guess this reflects different work styles.
#Conflicts: # NEWS.md # R/release.R
Co-authored-by: Jennifer (Jenny) Bryan <jenny.f.bryan@gmail.com>
#' If you use [devtools::submit_cran()] to submit to CRAN, information about the | ||
#' submitted state is captured in a `CRAN-SUBMISSION` file. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I removed a mention of devtools::release()
, since submit_cran()
is ultimately called in that case as well. Also removed the mention of CRAN-RELEASE
since it's been long enough now, since we switched to CRAN-SUBMISSION
(late 2021).
I remain ambivalent on a few bits of this, but am merging so this doesn't just stall out. |
use_release_issue()
checks default branch and pulls automatically.use_github_release()
automatically pushes, if safe.use_github_release()
just creates the release.use_version()
gainspush
argument.Fixes #1385. Closes #1678.
@jennybc I did not touch
check_current_branch()
, instead focussing on reducing the places in our release checklist where we previously needed to do manual pushes or puls