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

How to preserve refspec to patches and branches after the repo renamed 'master' to 'main' #49017

Closed
Nirmal4G opened this issue Mar 2, 2021 · 3 comments
Labels
area-Infrastructure question Answer questions and provide assistance, not an issue with source code or documentation.

Comments

@Nirmal4G
Copy link

Nirmal4G commented Mar 2, 2021

For all those who can't pull master, it has renamed to main.

To preserve refspec to patches and branches, just changing the heads/master to heads/main should work.

[remote "origin"]
	url = https://github.com/dotnet/runtime
-	fetch = +refs/heads/master:refs/remotes/origin/master
+	fetch = +refs/heads/main:refs/remotes/origin/master
	tagopt = --no-tags
[branch "master"]
	remote = origin
-	merge = refs/heads/master
+	merge = refs/heads/main

Putting this out there, if anyone else facing similar issue with git.

@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged New issue has not been triaged by the area owner label Mar 2, 2021
@dotnet-issue-labeler
Copy link

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

@Nirmal4G
Copy link
Author

Nirmal4G commented Mar 2, 2021

Alternative to #48357. For those who cannot change the default branch for obvious 😉 reasons.

@ViktorHofer
Copy link
Member

Closing in favor of #48357

@jkotas jkotas added area-Infrastructure question Answer questions and provide assistance, not an issue with source code or documentation. and removed area-Infrastructure-libraries labels Mar 2, 2021
@ViktorHofer ViktorHofer removed the untriaged New issue has not been triaged by the area owner label Mar 3, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Apr 2, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-Infrastructure question Answer questions and provide assistance, not an issue with source code or documentation.
Projects
None yet
Development

No branches or pull requests

3 participants