-
Notifications
You must be signed in to change notification settings - Fork 24
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
Move master
branch to main
#19
Comments
GitHub's support for default branch renaming means that, in general, pull requests that target the default branch will be correctly re-targetted. However, there are some edge cases, where this is not true. Some pull requests are automatically closed when the default branch is renamed and they cannot be re-opened. This happens when the PR-making branch, fork, or user no longer exists. (Literally, it appears to boil down to whether There is 1 open pull request in this repo that is at risk of auto-closing: A way to "rescue" the work on such a PR is described in isaacs/github#168 (comment). Here's the TL;DR:
message id: hardhearted_newt |
We're ready to rename This blog post announces the larger effort and explains how contributors can update their local environments: Here's the TL;DR:
message id: amused_halibut |
The
master
branch of this repository will soon be renamed tomain
, as part of a coordinated change across several GitHub organizations (including, but not limited to: tidyverse, r-lib, tidymodels, and sol-eng). We anticipate this will happen by the end of September 2021.That will be preceded by a release of the usethis package, which will gain some functionality around detecting and adapting to a renamed default branch. There will also be a blog post at the time of this
master
-->main
change.The purpose of this issue is to:
message id: euphoric_snowdog
The text was updated successfully, but these errors were encountered: