Once we have added all of the files we want in this commit we then commit our code to the repo. This is just like the Commit step when using Git. If you do change your mind on your purchase, don’t worry you have that receipt and can return them. You pay for your items, and you get a receipt with all of the details of your transaction. Once all your items have been scanned by the shop attendant and you’re happy with them all, you’re ready to make your purchase. It also allows team members to access your work so they can use it or add to it. Once committed, we’ll be able to store code on the cloud with GitHub to keep it safe. It's good to commit often and not to save all of your changes up for one big commit at the end. Eg: For personal expenses versus work expenses) You might want to put them through in separate transactions (just like at the shops if you want items of different receipts. You can include multiple files, but don’t have to add all of your changes at the same time. You can also do this from the command line with the following command: You can either do this in the VS Code Version Control extension by clicking the + icon next to the different files. At this point you will “stage” your changes. When you are happy with the code you have created, you’ll want to lock it in (and get it safely stored on the cloud in a minute). At this time, you still haven’t bought the items, you could take them off the conveyer belt at the last minute or ask the shop attendant to remove any scanned items before you make your purchase. When you’re shopping and you are happy with the items in your basket, you will go to the cash register and put your items on the conveyer belt to get scanned by the shop attendant. You are just typing in code, removing code, and saving code locally on your computer (or web editor). It's our normal coding process, it does not involve Git commands. You can put things into your basket whenever you like. In our example we:įirst you are browsing the shop. Let’s say we are shopping for a new outfit. Git commands get a lot easier when we think about it like a shopping trip. To answer questions 3, 4, and 5, an analogy will help us understand. You can just click the “new” button or the “+” button on the home page, and the give your repo a name and add any other details. It’s easy to create a new repo on GitHub once you have an account. You can manage who has access to your repo, review changes your team has made, and set up automations for testing and deployments (once you get past the basics). It will also have the version history of all the changes that have been committed to the project along the way. This project or repo will have all the files that you and your team create. There are LOTS of other features GitHub gives you (like options for testing your code, integrating with deployment systems, and more), but you don’t need to know about any of that to get started with. It is a way of using all the handy features of Git, whilst also backing up your code on the cloud and making it accessible to the rest of your team. GitHub is a cloud-based platform that runs on the Git protocol. It has features that allow you to have multiple people collaborating on the same code, ways to integrate conflicting changes different coders make as they work together, and many other handy things. Git is one implementation of version control and is the most popular and widely used option. There are lots of different implementations of version control. (ideal if a bug appears in your program and you want to figure out where it came from) In short, version control is the idea that we want to keep track of how our code is changing over time and have ways to get back to previous versions of our code. You’ve probably heard about Git and GitHub when discussing version control. I’ll cover the points in the blog below, but you can also get them in video form here: (For now, you can watch this video)įor extra Git tools, you can also check my blog, “ Git yourself a leg up – Git tools for teaching and teams”. You’ll also have the skills to get started on this Cloud Skills Challenge: “Get Learning with Git – Git skills and GitHub tools”.įor more concepts after you have these basics, I’ll be creating a new blog soon “Get Collaborative with Git” for how to use Git when working in teams. By the end of this blog you’ll have the tools you need to work on a solo project using Git and GitHub. These are just the very essentials you need to get started. What is version control about, and how are Git and GitHub involved?. In this blog, you’ll learn the absolute essentials of Git and GitHub: But worry no more here are the tips, tricks, and analogies that will help you get started with Git and GitHub. Using Git and GitHub can be a little intimidating at first.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |