Then, download the GitHub app ( Mac or Windows). To make it easier to manage this process, we are going to use the official GitHub Desktop app.įirst, sign up for a free GitHub account if you haven't already. Also, it automatically creates a folder for you and unzips the contents there. Most importantly, cloning maintains a connection back to the mothership so you can sync your changes to the cloud."Clone" just means "download from to your own computer", but it's better than downloading the ZIP: If you try to sync changes to the original course copy, it will (correctly) tell you that you don't have permission to, so you have to remember to fork as your very first step of any project.Īfter you fork the repo, you'll clone your fork. Syncing changes to your repo is how you will submit your work. That way, you can upload (known as "pushing" or "syncing", in GitHub terminology) your changes to it. Your copy will then live at a URL like this: When you "fork" one of the course repositories, all it means is "create a copy on your own account". You'll find the list of the repositories we'll work on during this course on the organization page (your course org is probably called something like appdevwinter2017): Įach repository's original URL will look like this: We call the top-level folder a "repository". All of our apps are just a folder with some files (maybe some HTML files, some CSS files, etc) and other folders in it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |