-
Notifications
You must be signed in to change notification settings - Fork 8
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
Add git_remotes folder and contents #95
base: main
Are you sure you want to change the base?
Conversation
|
||
We’ll discuss remotes in more detail in the next episode, while talking about how they might be used for collaboration. | ||
|
||
### SSH |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should SSH become its own module that can then be a prereq here? It just seems like a pretty lengthy detour from the main content of the module.
$ git init | ||
``` | ||
|
||
If you remember back to the earlier episode where we added and committed our earlier work on mars.txt, we had a diagram of the local repository which looked like this: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should I remove these SWC diagrams since they weren't used before? I could replace with a text description harkening back to the language ED used in the Understanding the git workflow module
Make push and pull own pages
Already up-to-date. | ||
``` | ||
|
||
Pulling has no effect in this case because the two repositories are already synchronized. If someone else had pushed some changes to the repository on GitHub, though, this command would download them to our local repository. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Example to show what intervening changes and pulling would look like?
|
||
**Pulling** remote changes into your local repository means you are getting any changes pushed to the remote repository and using the files in that state to perform add your own changes. | ||
|
||
Remebering to push and pull changes is especially important when collaborating with others. Others cannot see or work with your changes if you do not push them. You may be working from an outdated version of your repository if you do not pull changes prior to starting out. Forgetting one or both of these steps may lead to conflicts in Git. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Link to conflicts module when it's complete.
|
||
What we will do now is the minimum required to set up the SSH keys and add the public key to a GitHub account. | ||
|
||
<div class = "warning"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Confirm with someone else? Definitely true for me but not sure if universal
add Attribution section with our own CC license HTML
Attribution>Addt'l Resources and add @source_attribution there
No description provided.