Комментарии:
Thanks man.....
ОтветитьThanks so much for your detailed instruction!
ОтветитьThank you very much!!! You are save me! I'm stuck on this error for a few hour & saw your video. That is very HELPFUL! THANKYOU! <3
ОтветитьLIKE
Thank you, I was a little bit annoyed and frustrated with GitHub,
I mean they could make this whole thing simpler, but they decided not to!
thanks my brother you saved my life on my project.
Ответитьgit pull origin master
fatal: couldn't find remote ref master
thanks very much... your video was perfectly explained and helped alot
ОтветитьOld but gold♥
ОтветитьThanks man.
ОтветитьHi Kevin.
Thanks for the fix! I was really confused and tried many methods (like deleting the file and creating a new file with the same name).
Great explanation of the topics!
The suggestions to prevent the problem that you provided are only accurate if you're the only one pushing and pulling to and from the repo; i.e., it's not a collaborative project. I ran into this issue when another colleague pushed a commit to the repo, creating a new file that I didn't have on my local machine, and I attempted to push my code changes.
ОтветитьVery good. Thanks!
ОтветитьCan not we push forcefully, without pulling etc
ОтветитьWonderful, simple and stright forward,,,You forced me to subscribe.
ОтветитьYou just saved me from having to do further research to solve an issue I encountered while using Github. Thanks man. Muito obrigado!
Ответитьgreat thanks!!!!
ОтветитьYou jjust saved a life. Thanks for sharing this video
ОтветитьThat 2nd option helped me...thanks for the quick and easy solution
Ответитьthis is still ok in 2020. thanks man.
ОтветитьThis one help me! Thank you,
ОтветитьBe noted! Now `master` branch name has been changed to `main` in Github, that is a change effected from Oct.2020.
Ответитьthank you , now I understand my problem
ОтветитьThank you for this!
ОтветитьAfter I pulled, it still gave me the error.
ОтветитьThank you, you are a life saver.
I was going crazy because of this issue and I didn't know how to troubleshoot it, and then I started doubting whether I will ever make it as a software developer, then I doubted my entire existence, and I almost cried.
This was yesterday and today I saw your video and finally fixed my error.
Thank you so much!
Thank you.
ОтветитьGood help :)
ОтветитьThank you from somebody who is just learning how to do lines of code ... again: thank you very much !
Ответитьthanks! But sometimes I need to do "git pull origin master --allow-unrelated-histories".
ОтветитьThank you. This video was very helpful.
Ответитьis there a way to clear those files that were initialized in the github console?
ОтветитьThanks! Very much, Now I can get my repo updated.
Ответитьif anyone has "refuse to me merge unrelated histories" error, run "git pull origin master --allow-unrelated-histories"
Ответитьthanks... I am newbie to programing world and you tutorial helps me a lot
Ответитьit works for you and it doesn't work for me
Ответитьthankyou so meri jaan.....
Ответитьnice you fix my problem
ОтветитьGreat video!
Ответитьthank you very much!!!
Ответитьexcelente video me ayudo bastante
ОтветитьNO change, still the sae issue occurs
ОтветитьThank you. This helped a lot
ОтветитьGood tutorial! The cloning method worked for me in 2019, except I also had to run "git pull origin master --allow-unrelated-histories" to resolve the "fatal: refusing to merge unrelated histories " error.
ОтветитьVery helpful
ОтветитьCould you show the same using GIT GUI ?
Ответитьgit pull origin master //not working
ОтветитьYour video is good, BUT, to make it good enough, i would really appreciate it if you can direct me to where i can learn all the git commands via the command prompt aka CMD
Ответитьman you save me!! thanks so much!
Ответитьthanks. i found the best way to be clone.
Ответить