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.

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

⚠️🚧👷 Scheduled rename master branch to main #116341

Closed
joaomoreno opened this issue Feb 10, 2021 · 5 comments
Closed

⚠️🚧👷 Scheduled rename master branch to main #116341

joaomoreno opened this issue Feb 10, 2021 · 5 comments
Assignees
Labels
engineering VS Code - Build / issue tracking / etc. insiders-released Patch has been released in VS Code Insiders
Milestone

Comments

@joaomoreno
Copy link
Member

joaomoreno commented Feb 10, 2021

On Feb 14, 2021, 8PM UTC the microsoft/vscode repository will rename its master branch to main.

cc @microsoft/vscode


⚠️ Call to Action ⚠️

If you have a clone of microsoft/vscode locally, you'll need to run the following commands after the rename happens:

git branch -m master main
git fetch origin
git branch -u origin/main main
git fetch --prune
@joaomoreno joaomoreno added the engineering VS Code - Build / issue tracking / etc. label Feb 10, 2021
@joaomoreno joaomoreno self-assigned this Feb 10, 2021
@joaomoreno joaomoreno added this to the February 2021 milestone Feb 10, 2021
@joaomoreno joaomoreno pinned this issue Feb 10, 2021
@joaomoreno joaomoreno changed the title ⚠️ Scheduled rename master branch to main ⚠️🚧👷 Scheduled rename master branch to main Feb 10, 2021
@baslr
Copy link

baslr commented Feb 11, 2021

Women can also be a construction worker 👷‍♀️ 🤦‍♀️

@joaomoreno
Copy link
Member Author

Women can also be a construction worker 👷‍♀️ 🤦‍♀️

@baslr Absolutely, why would you even think otherwise?

In this case, I am the one doing the construction work and I happen to be a man... I think. 🤔

@solarblueberry
Copy link

May I ask why is this necessary? Did I miss something?

@foreignmeloman
Copy link

May I ask why is this necessary? Did I miss something?

I guess the same reason why GitHub defaults to 'main' master branch name now. Good old PC BS. Apparently word 'master' has a bad stigma attached to it now 🤦‍♂️

@joaomoreno
Copy link
Member Author

joaomoreno commented Feb 11, 2021

Guys & gals, I'm sorry. Nothing bad happened here, but I'm just going to lock this thread right now before it does.

As a team, we've decided to go ahead with this rename, because reasons. This issue isn't the place to discuss the merits and drawbacks of the rename. If you feel like venting, I recommend you do so through your own personal mechanisms. Mine is running 10k out in the cold. 🏃

@microsoft microsoft locked as too heated and limited conversation to collaborators Feb 11, 2021
@meganrogge meganrogge unpinned this issue Feb 25, 2021
@meganrogge meganrogge pinned this issue Feb 25, 2021
@jrieken jrieken unpinned this issue Mar 5, 2021
lemanschik pushed a commit to code-oss-dev/code that referenced this issue Nov 25, 2022
lemanschik pushed a commit to code-oss-dev/code that referenced this issue Nov 25, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
engineering VS Code - Build / issue tracking / etc. insiders-released Patch has been released in VS Code Insiders
Projects
None yet
Development

No branches or pull requests

5 participants
@joaomoreno @baslr @foreignmeloman @solarblueberry and others