Skip to content

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

Merged
merged 17 commits into from
Mar 5, 2023
Merged

Reduce number of manual git release steps #1746

merged 17 commits into from
Mar 5, 2023

Conversation

hadley
Copy link
Member

@hadley hadley commented Jan 20, 2023

  • 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() gains push 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

* `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()` gains `push` argument.

Fixes #1385. Closes #1678.
@hadley hadley requested a review from jennybc January 20, 2023 13:48
Copy link
Member

@jennybc jennybc left a 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.

@hadley hadley requested a review from jennybc January 30, 2023 18:05
Comment on lines +214 to +215
#' If you use [devtools::submit_cran()] to submit to CRAN, information about the
#' submitted state is captured in a `CRAN-SUBMISSION` file.
Copy link
Member

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).

@jennybc
Copy link
Member

jennybc commented Mar 5, 2023

I remain ambivalent on a few bits of this, but am merging so this doesn't just stall out.

@jennybc jennybc merged commit 6c2012b into main Mar 5, 2023
@jennybc jennybc deleted the auto-push branch March 5, 2023 17:50
jennybc added a commit that referenced this pull request Mar 10, 2023
jennybc added a commit that referenced this pull request Mar 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Update TODO note in usethis::use_github_release() Should use_github_release() offer to push if needed?
2 participants