Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Rename default branch master to main #153

Closed
4 tasks done
ben-clayton opened this issue Jun 15, 2020 · 5 comments
Closed
4 tasks done

Rename default branch master to main #153

ben-clayton opened this issue Jun 15, 2020 · 5 comments

Comments

@ben-clayton
Copy link
Member

ben-clayton commented Jun 15, 2020 •
edited

main is more inclusive and is being increasingly adopted as the default branch name. Let's switch.

Tasks:

  • Create new main branch from master
  • Update all CI / package references to point to main (done except for vcpkg)
  • Merge any late landing changes from master to main (Merge master to main #158)
  • Delete master branch
ben-clayton added a commit that referenced this issue Jun 15, 2020
@ben-clayton
README.md: Repoint link from master to main
c512711 
See #153
@ben-clayton ben-clayton mentioned this issue Jun 15, 2020
Closed
@ben-clayton
Copy link
Member Author

SwiftShader change:
https://swiftshader-review.googlesource.com/c/SwiftShader/+/45769

@ben-clayton
Copy link
Member Author

SwiftShader change landed.

ben-clayton added a commit to ben-clayton/vcpkg that referenced this issue Jun 17, 2020
@ben-clayton
[marl] Repoint HEAD_REF to main
7f4705a 
The default branch has been renamed from `master` to `main`.

See google/marl#153 for more details.
sagpant pushed a commit to sagpant/swiftshader that referenced this issue Jun 17, 2020
@ben-clayton
Repoint marl branch from master to main
af80f85 
See google/marl#153 for more details

Bug: b/140546382
Change-Id: I73cd3e575b781890e82eda94285e8a585bd879d5
@fulldecent
Copy link

Hello @ben-clayton are you able to help reference an internal, authoritative policy at Google that motivates this change? (Rather than just common sense.)

If you have it, it would be useful for me to cite in other Google projects that are considering to make this same change.

Thank you.

@fulldecent fulldecent mentioned this issue Apr 25, 2021
Closed
@ben-clayton
Copy link
Member Author

Hello @ben-clayton are you able to help reference an internal, authoritative policy at Google that motivates this change? (Rather than just common sense.)

Hi @fulldecent, I'm afraid I don't have any links I can share publicly.
That said, if a Googler asks for such links, you can certainly point them my way!

Many thanks,
Ben

@fulldecent
Copy link

That's perfect, thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@fulldecent @ben-clayton