Thank you for the simplicity of this video. It really helped me a lot!

One of the simplest explaination

I felt like I was in a classroom with my favorite professor and I watched till the end. Good one.

The most simplest and clearest tutorial about this subject ! thank you so much for this content.

Thank you. I think it boils down to one thing > "Access Control". People should tell this from the beginning. In my understanding ... you just don't want to have people to be able to push unrestricted. - People who can push unrestricted = Clone - People who can not push unrestricted = Fork + Advantage of Fork = New Admin Rules.

@russelllewis9215

Жыл бұрын

Agreed. I like to put a focus on the same-ness, but you're right about where the difference lies.

@b25671

Жыл бұрын

​@@russelllewis9215 As others who have written here... You're about the only one who actually mentioned the core difference. (in my understanding... I'm sure there is more going on under the hood). Thank you for your great explanation!

Best video for understanding fork n clone. The way you explain is outstanding. 👍🏻👍🏻

Great explanation!

Thanks man. Super detailed and nicely explained

This was such a great explanation! Loved it :)

Thank you so much man. This is an absolute eye opener for people beginning to learn git and github.

Great video and explanation

Very well explained!!

Thank you!

absolutely simple, thank you so much!

Thanks so much for this information, you saved me alot of stress trying to push to a remote I had no collaborative access.

NICE

Nice video! very interesting and clear. Also, insane beard! so good :D

a moment of SILENCE for those who imagined perfectly cutting that beard just for a satisfaction

thanks a lot

This is the best explanation! Thanks a lot for the video tutorial. Subscribe, like, good luck!

Took me back 40'ish years so well that I felt like I should be taking notes for the final exam! 😅 You must teach professionaly somewhere? (or you could)

But even with from trusted people ..we cannot simply accept the push right?...what if the trusted one became rogue and trying to do some ill things with the repository ?... how admin verify such things? do admin have the option to verify ? before they can accept the push ...if so how admin is viewing it?...if admin can verify before accepting the push...then what is the use of fork?..it does the same thing.

@russelllewis9215

Жыл бұрын

Agreed, but that's the point of the administrative boundary. You only give permissions to the small number of people you trust. If you want to approve somebody's work, then a fork/pull-request model makes more sense.

@girirajrdx7277

Жыл бұрын

@@russelllewis9215 So once someone was given a push permission... its like giving someone a gun ,hoping they do only good things with that? Also i am expecting more videos on git(like branches, and other stuffs that devs usually do on a typical work day) I really like your flavour of explaining things.

@russelllewis9215

Жыл бұрын

@@girirajrdx7277 :)

IMHO explanation is unnecessary long, but its the only tutorial that actually explains the conceptual difference of clone vs fork. the key sentence is, that the receiver of a pull-request can't access the senders repo to do the requested pull, when the repo was only cloned to senders local computer.

@russelllewis9215

3 жыл бұрын

It's true, I *do* tend to make my explanations pretty long. :)

@klaus-udokloppstedt6257

3 жыл бұрын

@@russelllewis9215 don't worry to much :). it helped me to understand, with this ahhh-moment, followed by 'of course!'.

@girirajrdx7277

Жыл бұрын

if you already have an idea about it ..it do feel like unnecessary ...but somebody completely new to the area ..needed this kinda of explanation which strongly cements the concept in students brain ....and while other explanations may get a follow up question to completely understand ..his way doesnt need any follow up question to properly understand since everything is explained so well that they start or helps their fellow folks with much ease.