https://deploy-preview-149--peppy-otter-7a55ad.netlify.app/01-getting-started-with-git-and-github/index.html Let’s start with some practical exercises! In this chapter we’ll be creating a new repository locally and on GitHub, making and versioning changes and pulling and pushing changes to GitHub Hugo en-us Wed, 05 Aug 2020 18:26:54 +0100 https://deploy-preview-149--peppy-otter-7a55ad.netlify.app/01-getting-started-with-git-and-github/00-typical-workflow/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://deploy-preview-149--peppy-otter-7a55ad.netlify.app/01-getting-started-with-git-and-github/00-typical-workflow/index.html In a typical Git + GitHub workflow, you’ll have have your work in a folder (repository) on your local computer and also a linked copy on a remote repository (origin), in this case GitHub. You can make changes in your local repository (most common) or your remote repository. To synch the remote repository with local changes you Push. https://deploy-preview-149--peppy-otter-7a55ad.netlify.app/01-getting-started-with-git-and-github/01-configure-git-profile/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://deploy-preview-149--peppy-otter-7a55ad.netlify.app/01-getting-started-with-git-and-github/01-configure-git-profile/index.html Before we start, if you did not configure your git profile when first launching GitKraken Client, you can do this by clinking on the avatar in the top right corner, selecting the profile to edit and clicking on Edit A Profile in the client. Next complete the details with the username and email you used to sign up to GitHub and save. Git has now been configured with these details. https://deploy-preview-149--peppy-otter-7a55ad.netlify.app/01-getting-started-with-git-and-github/02-create-first-repo/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://deploy-preview-149--peppy-otter-7a55ad.netlify.app/01-getting-started-with-git-and-github/02-create-first-repo/index.html Creating your first repository When a local directory becomes initialised with git, a hidden .git folder is added to it. It’s now called a repository. You can initialise an existing project with git or a start with a completely new project. We’ll start by creating a new repository. In GitKraken Client, make sure you’re logged in to GitHub. https://deploy-preview-149--peppy-otter-7a55ad.netlify.app/01-getting-started-with-git-and-github/03-add-file-to-repo/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://deploy-preview-149--peppy-otter-7a55ad.netlify.app/01-getting-started-with-git-and-github/03-add-file-to-repo/index.html Okay! Now we need to do something with the repository. Let’s start with a basic use-case and make a single file that lists some to-do items. The repository is just a normal folder on your computer where you can create and edit files like normal. Open the folder (repo) you have just created. In GitKraken Client, you can do this by going to File > Open in File Manager. Now create a file in this folder. Open your favourite text editor and use to create a new TODO.txt file. https://deploy-preview-149--peppy-otter-7a55ad.netlify.app/01-getting-started-with-git-and-github/04-check-out-git-history/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://deploy-preview-149--peppy-otter-7a55ad.netlify.app/01-getting-started-with-git-and-github/04-check-out-git-history/index.html Check out the Git history Now, if you look at the history of the repository you can see two commits. The first was automatically done by GitKraken Client when you created the repository - and the second should be yours! https://deploy-preview-149--peppy-otter-7a55ad.netlify.app/01-getting-started-with-git-and-github/05-make-some-changes/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://deploy-preview-149--peppy-otter-7a55ad.netlify.app/01-getting-started-with-git-and-github/05-make-some-changes/index.html We’ve gotten some work done, so we’d like to update our to-do list: Update the list with all the tasks we have completed. Add any pending tasks Commit and push the changes in the TODO.txt. Don’t forget to type a summary message before you commit! https://deploy-preview-149--peppy-otter-7a55ad.netlify.app/01-getting-started-with-git-and-github/06-pulling-from-remote/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://deploy-preview-149--peppy-otter-7a55ad.netlify.app/01-getting-started-with-git-and-github/06-pulling-from-remote/index.html Push makes sure that your work is not only in your computer but “online” as well which means: It is backed up. You can access it from any location. If your repository is open, other people can benefit from your work, they can contribute, reference you or even make recommendations. Now, what if you you make changes directly on the GitHub repository or using another machine? These changes are not locally synchronized with your primary computer. This is where pull comes into play. https://deploy-preview-149--peppy-otter-7a55ad.netlify.app/01-getting-started-with-git-and-github/07-git-tips/index.html Wed, 05 Aug 2020 18:26:54 +0100 https://deploy-preview-149--peppy-otter-7a55ad.netlify.app/01-getting-started-with-git-and-github/07-git-tips/index.html 1. commit early, commit often 2. commit logical bits of work together 3. write meaningful commit messages Always remember