Go back to the index for the all the Git stuff.
Go to https://github.com and make sure you are logged in.
Click green “New repository” button. Or, if you are on your own profile page, click on “Repositories”, then click the green “New” button.
Repository name: myrepo (or whatever you wish, we will delete this)
Public
Check Initialize this repository with a README
Click big green button “Create repository.”
Copy the HTTPS clone URL to your clipboard via the green “Clone or Download” button.
Open GitKraken.
Click the folder icon in the upper left corner.
Chose Clone a repo. Clone means to make a copy of the repository on your computer.
Note: Where to clone to should be the Repositories directory you set up as your first step.
Your repository should show below. Click it and Clone the repo! at the bottom of the screen.
If things are happy you should get a nice satisfying “Successfully clone the repo” at the top with a prompt to Open Now or Ok. If you click Open Now, your new repo version history will show in the main window. It will be empty because you haven’t done anything but an Initial commit.
Add a line to README using a text editor and verify that Git notices the change.
Change: Type one or more lines in your README.md file and save. When saved you should notice in GitKraken on the right that README.md shows up in the unstaged box. This is saying changes have been made to this file but version control hasn’t occurred yet.
Next you will stage the files with changes that you want to be remembered by version control. Normally this will be everything, but perhaps not all the time. For now ‘Stage all changes’ (the green button on the right towards the top).
Commit: Next you will add a line saying what you changed in the Summary box in Commit Message. Perhaps something like, ‘Added required text to test system.’ Then ‘Commit’ (green button on the bottom). If things are happy, you will see your comment on the left. You have just done version control on your local computer.
Push: Pushing is sending these changes in your files to GitHub for public/private viewing. This is like DropBox syncing your changed files. To Push click the up arrow in the middle of the top bar. You should get a “Pushed successfully” pop-up window on the right.
If you’re a new GitHub user, you may be be challenged for your GitHub username and password. Provide them!
Go back to the browser. I assume we’re still viewing your new GitHub repo.
Refresh.
You should see the new “text I added on my computer” in the README.
If you click on “commits,” you should see one with the message “Added required text to test system.”
Let’s pretend that you went to bed after this excise and now you want to add more changes to README. Good practice is to first pull (using the down arrow) from GitHub before starting. This will assure you are working with the most recent version of the documents. Since you might be collaborating, it is possible that your local version isn’t up-to-date. Maybe your collaborators works later in the night than you. Although we won’t do this now, it is worth mentioning.
When you’re ready to clean up, delete the local Repositories folder.
In the browser, viewing your repo’s landing page on GitHub, click on “Settings”, near the bottom or the right sidebar.
Scroll down, click on “delete repository,” and follow the instructions.
Go back to the index for the all the Git and GitHub stuff.