-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Switch all googleapis python repos to use a default branch of main #10579
Comments
@dandhlee @plamut FYI this PR provides a one-liner to pull and run the migration script via cURL; the main-migration branch within google-cloud-python holds the scripts, so if they need to be updated or modified, you will be able to access the most recent versions via cURL. (for example, I just pushed a PR that uses "chore:" instead of "docs:" for the commit message) |
@nicain Thanks, that's useful. One side note, the name of the remote is hardcoded and assumed to be In addition, not all references to Something to keep in mind if anybody else uses a similar setup and if a repo has its own specifics. Best to read the script source first, it's pretty short and straightforward anyway. |
@dandhlee, @parthea PR needing review: googleapis/python-bigtable#411 |
All task are complete |
Please follow these steps to change the default branch from master to main:
master
in the repository. Open a PR in the repo to replace the termmaster
withmain
. We have automation which will revert changes made to templated files so we also need to add replacements inowlbot.py
to replacemaster
withmain
similar to this PR. See this bash script that I used to create the branch for the linked PR. Note: Once this synthtool PR is merged and the synthtool templates have propagated to the repo via owlbot, we can remove the replacements in owlbot.py added in this step.The text was updated successfully, but these errors were encountered: