In the last post, I talked about how to create a Git repository and upload it to GitHub. In this post, I’m going to talk about how to resolve Git conflicts.
Setting Up Our Environment
First, we’re going to create a Git Repository for the user Doug. Since I already covered that in the last post, I’m bring to breeze through those steps below:
$ mkdir doug
$ cd doug
$ git init
Initialized empty Git repository in /path/to/doug/.git/
$ touch README.md
$ git add README.md
$ git commit -m "First commit"
[master (root-commit) d86a7e2] First commit
1 file changed, 0 insertions(+), 0 deletions(-)
create mode 100644 README.md
At this point, we have a repository created for the user Doug. Now I’m going to clone that repository for the user Andrew:
Continue reading “Git 101: How to Handle Merge Conflicts”
In this post, I’m going to discuss how to create a GitHub repo and upload (or “push”) it to GitHub, a popular service for hosting Git repositories.
What is revision control and why do I need it?
The concept of revision control is a system which tracks changes to files. In programming, that is usually program code, but documents and text files can also be tracked. Using revision control will give the following benefits:
- You will know what was changed, when it was changed, and who changed it
- Multiple people can collaborate on a project without fear of overwriting each others’ changes.
- Protection against accidentally deleting a critical file. (revision history is usually read-only)
In GitHub, we store revisions in “repositories” or “repos” for short. As of this writing, the #1 service for storing Git repositories is GitHub. They offer free hosting for Git repositories.
Continue reading “Git 101: Creating a Git Repo and Uploading It To GitHub”