assignUser commented on issue #2173: URL: https://github.com/apache/arrow-rs/issues/2173#issuecomment-1335155487
> Keep master branch up to date for a while, add some deprecation notification in the master branch This is not necessary, github will forward `master` to the new default branch and a bunch of other stuff ([from](https://github.com/github/renaming#renaming-existing-branches) ) > - Retarget any open pull > - Update any draft releases based on the branch > - Move any branch protection rules that explicitly reference the old the branch used to build GitHub Pages, if applicable > - Show a notice to repository contributors, maintainers, and admins on the repository homepage with instructions to update local copies of the repository > - Show a notice to contributors who git push to the old branch > - Redirect web requests for the old branch name to the new branch name > - Return a "Moved Permanently" response in API requests for the old branch name So unless there is a bunch of tooling with `master` hard coded (e.g the issue over in apche/arrow) renaming should be pretty painless. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: github-unsubscr...@arrow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
