[Known issue] Your configuration specifies to merge with the ref 'refs/heads/master' from the remote, but no such ref was fetched

[jkroll-aws]

This message occurs now that the default branch has been renamed to "main", but your clone is still attempting to pull from "master".

To resolve this issue, run the following CLI commands in your local cloned repository:

git branch -m master main
git fetch origin
git branch -u origin/main main
git remote set-head origin -a

This will allow you to continue to pull the latest commits as usual.

Please refer to the announcement: https://github.com/aws/amazon-sagemaker-examples/discussions/3131

[DenisOuma]

this was so helpfull

[jlnbuiles]

i had this issue with develop. what had happened to me (and may happen to others) is that we accidentally deleted develop on remote while merging a PR. so make sure that you haven't accidentally deleted your branch though a PR merge 😌 .

[davidgsd]

I love it when I get a bunch of complicated git errors and then do a search, click on the first link that comes up, run jkroll-aws' 4 commands and everything then works perfectly : )

[blackmonk69]

you saved my life, thanks bro

[DarkOwn3r]

Thank you so much! This solved my problem when the main on origin was renamed to main and tried to git pull.

[CrazyFranck23]

I'm a newbie in using git and github and finding a rapid solution at my first error is so fantabalous. Thanks very much !! I just had to use the first command line and everything was OK.

[Driton-Gashi]

Thanks man, very helpful

[sbichpuriya11]

After following above steps getting this error>>>fatal: refusing to merge unrelated histories

[julianaconsolati]

Super helpful! Thanks! 😄