Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Episode 07] [Episode 08] - mention why origin nickname is so common #359

Open
pshriwise opened this issue Nov 2, 2016 · 3 comments
Open

[Episode 07] [Episode 08] - mention why origin nickname is so common #359

pshriwise opened this issue Nov 2, 2016 · 3 comments

Comments

@pshriwise
Copy link
Contributor

@pshriwise pshriwise commented Nov 2, 2016

Might be a good idea to indicate why this nickname is the most common because it is the default nickname in git when cloning a remote repository. This could be good to indicate explicitly in lesson 08 as well to reduce confusion. Maybe even add a quick git remote -v command to show the user it was automatically created.

@swaldman3
Copy link
Member

@swaldman3 swaldman3 commented Nov 3, 2018

I'm happy to make this change as my instructor checkout PR, but... er... can anybody tell me why origin is the convention? A few minutes on google didn't help.

Loading

@pshriwise
Copy link
Contributor Author

@pshriwise pshriwise commented Nov 5, 2018

Hi @swaldman3 - thanks for picking this up!

I don't know of a particular reasoning behind choosing origin as the default remote name other than its meaning (to me) is something like "this is the origin of the clone you made". My take is that the important part for the learners is that it will be there when they clone repos, and is simply (as you said) a convention in git.

If you're willing, a note explaining a bit more on remotes as aliases to other repos with commands for renaming/changing them would probably be helpful to some as well!

Loading

@pshriwise
Copy link
Contributor Author

@pshriwise pshriwise commented Nov 5, 2018

Looking at the lessons again, some of this is explained in Episode 8, but I think knowing these things upon first seeing that remote name will reduce confusion. Maybe that note I alluded to would be better placed in Episode 8 after the git remote -v command is introduced.

Loading

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants