# 0.3: GitHub ## Learning Objectives 1. GitHub is a code-hosting website that hosts Git repos for individuals or teams to review and collaborate on 2. Know how to fork a repo on GitHub 3. Know how to clone a repo from GitHub 4. Know how to push changes to GitHub 5. Know how to pull changes from GitHub 6. Know how to view repo commit history in GitHub ## Introduction GitHub is a code-hosting website that hosts Git repos for individuals or teams to review and collaborate on. Team members can easily review latest code changes and commit history, making software development more transparent and thorough. ## GitHub Workflow Summary 1. **Fork** repos we do not have edit access to to suggest changes or maintain our own copy 2. **Clone** repos to download local copies of GitHub repos 3. Once we have committed the changes we want locally, **push** our changes to GitHub to share them with others. Refresh the GitHub repo page to see those changes. 4. If we are working with teammates and wish to download their code while keeping local changes, **pull** their code from GitHub after committing our local changes. ## GitHub Fork A GitHub "fork" is a copy of another GitHub repo. SWEs typically "fork" repos they do not have edit access to either to make improvements to merge back into original repos, or to create and maintain independent versions of repos. At Rocket Academy we will fork Rocket exercise repos to complete and submit assignments. We can fork a repo by clicking the Fork button on a GitHub repo page. Once forked, we can change our copy of the repo without affecting the original. ![Click the Fork button to fork a repo](/files/mYshD9ZNtpVul6aCoomx) ![Fork menu; We typically keep the same repo name for clarity](/files/ORAkJJZzwXh6AOXzinoE) ![Forked repo; Notice the repo is now under my account](/files/sBFoOxSCuK8AAZdLgrrL) ## Git Clone Once we have edit access to the repo we want to edit, either by forking an existing repo or [creating a new repo](https://docs.github.com/en/get-started/quickstart/create-a-repo), we can "clone" (i.e. download) that repo to our local machine to make changes to it. Click the copy button in the Code dropdown menu on the GitHub page of the repo we wish to edit. ![Click the copy button in the Code dropdown to copy the repo link to use with git clone](/files/sUJQQxtdawtF9IuQcWx7) Then go to terminal, `cd` to the relevant folder and enter the command `git clone `, where `` is the URL we just copied from GitHub. This will create a new folder named after the repo with the repo's contents inside. ``` bootcamp % git clone https://github.com/kai-rocket/react.git Cloning into 'react'... remote: Enumerating objects: 203678, done. remote: Total 203678 (delta 0), reused 0 (delta 0), pack-reused 203678 Receiving objects: 100% (203678/203678), 173.82 MiB | 5.85 MiB/s, done. Resolving deltas: 100% (144768/144768), done. bootcamp % ``` Once we've cloned the repo we can make edits to it and track our changes with Git. ## Git Push `git push` allows us to share local changes by "pushing" local commits to GitHub for others to view. Video demo below. {% embed url="" %} Demonstration of how to push local changes to GitHub {% endembed %} ## Git Pull `git pull` allows us to download new changes in a shared GitHub repo (e.g. by teammates) while keeping our local changes. Git will automatically merge downloaded and local changes, and let us know if there are "merge conflicts", for example if downloaded and local changes edit the same lines of code. We will work more with `git pull` once we start group projects. ## How to view commit history in GitHub GitHub provides an easy way to view past changes to a repo. For example, if we are wondering which commit changed a line of code that caused a bug, we can easily find which commits changed that line, who made those commits and what other changes were in those commits. ![Click the number of commits on a repo's GitHub page to view a list of all its commits](/files/jK8mYwl98OmI13oxShA1) ![Click on any commits in the repo's commit history to view the details of that commit](/files/d1YlKWFpwoOQ4Bis74yg) ![We can review complete details of each commit in GitHub](/files/kvzFZ4XrY4esKKpEqkYg) ## Additional Resources 1. [Git and GitHub in Plain English](https://blog.red-badger.com/2016/11/29/gitgithub-in-plain-english) (blog post) 2. [Git and GitHub by The Coding Train](https://youtube.com/playlist?list=PLRqwX-V7Uu6ZF9C0YMKuns9sLDzK6zoiV) (video playlist) 3. (Below) Intro to GitHub video from prior version of Rocket's Coding Basics course 4. (Below) GitHub Fork video from prior version of Rocket's Coding Basics course 5. (Below) GitHub Repo Browsing video from prior version of Rocket's Coding Basics course {% embed url="" %} Intro to GitHub video from prior version of Rocket's Coding Basics course {% endembed %} {% hint style="warning" %} In the below GitHub Fork video we demonstrate `git push origin master`, but for most purposes `git push` will suffice. {% endhint %} {% embed url="" %} GitHub Fork video from a prior version of Rocket's Coding Basics course {% endembed %} {% embed url="" %} GitHub Repo Browsing video from prior version of Rocket's Coding Basics course {% endembed %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://bc.rocketacademy.co/0-foundations/0.3-github.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.