DEV Community

Cover image for Forking Cloning Github
overFlow
overFlow

Posted on

Forking Cloning Github

Hacktober

The #hacktoberFest inclined learning continues.
I have learned just how important the ReadMe file is. And how the Code of Conduct file is also important. Especially if you are intent on making communication.
Then the licence file also. If you care to know for what type of cause you are contributing to.

I spent a good week learning git in August. I loved it. It was awesome.
It was one of the best lessons I ever had. As much as it was short. And as much as I later discovered that there is more to learn.
I learned all I think I thought I needed to learn.
I learned how to :
git --ver; git init; git ccommit; git config; git add; git clone; git branch. etc

Simple stuff but learning can also be dangerous. I learned to git fork. But I was never aware that the forked files went into my repository.
It is only now that I have realised that. I do not know how!! please do not ask me how lol!!!

But I guess we all learn. I am happy I learned this. It puts things into better perspective. lol.

On to the next one.

Git clone.

The project repository is called the upstream. And the remote is called the origin remote.
Another lesson clarified. The difference to me was not there.
There was a confusion on my part between upstream and origin remote.

So What Im doing now is making a html page. And creating a repository for it. I know there is way to upload it and that is what
I am gonna do and I wanna see how things will work.
That is one. And then two:

I guess some lessons are immersive lessons. And some deep; some shallow. But then again some immersion needs to be repeated.
Double dipped. triple dipped.

I just now looked at another blog and its got 19 steps.
I think I will be gone for while.

Top comments (0)