I'm a self-taught dev focused on websites and Python development.
My friends call me the "Data Genie".
When I get bored, I find tech to read about, write about and build things with.
I'm a self-taught dev focused on websites and Python development.
My friends call me the "Data Genie".
When I get bored, I find tech to read about, write about and build things with.
And if you are working on a fork, it is useful to have two remotes. One is "origin" for your fork. And one is named "upstream" usually and references to the original repo.
I'm a self-taught dev focused on websites and Python development.
My friends call me the "Data Genie".
When I get bored, I find tech to read about, write about and build things with.
Indeed,
origin
is the remote and the name origin is the default or convention.after you clone, you can see your remote.
And you can see what it points to. You might use GitHub or BitBucket here.
I guess you could make the fetch and push different but never had to do that.
And if you are working on a fork, it is useful to have two remotes. One is "origin" for your fork. And one is named "upstream" usually and references to the original repo.
View
Verbose
Your push and pull operations will use origin by default
And now you can pull the original repo into your fork!
I have notes here if you are interested
michaelcurrin.github.io/dev-cheats...
michaelcurrin.github.io/code-cookb...