Skip to content

Latest commit

 

History

History
149 lines (133 loc) · 11.5 KB

github-collaboration.md

File metadata and controls

149 lines (133 loc) · 11.5 KB
Raw

GitHub Collaboration

Projected Time

About 1 hour

  • 30 minutes for slides/Guided Practice
  • 20 minutes for Independent Practice
  • 10 minutes for small group discussion

Prerequisite

  • Git version control lesson
  • Git code storage lesson
  • Terminal or Command Prompt

Motivation

-In the industry, apps are created by teams of developers rather than individual people. Proper use of GitHub for collaboration minimizes code conflicts and helps teams work together.

  • At the heart of collaboration, developers use branches when working on new features or patching a bug. This makes it easier to deal with multiple contexts while developing in a professional manner. To elaborate, every bug patch or new feature is a context because it is unique to itself and thus is considered as something clearly separated from other things. Branches allow seamless and simultaneous developement of these in a manner that allows full focus on each context in its own environment.
  • Pull requests (PRs) are how developers include contribution in the intended repository. It lets you tell the repository owners or maintainers about your changes, after which it can be reviewed and included if satisfactory.

Who uses GitHub: As of August 2019, more than 40 million people use GitHub. Some popular companies are Facebook, Google and Microsoft.

Looking at an example repository If you have checked a repository before, you might have noticed it says Branch: master right under the tabs and metadata. That button can be used to switch and subsequently check various branches.

  • For example, you can view various branches on Facebook's React repository. Notice how the branches are adapted for various purposes.
  • Similarly you can also check pull requests on Facebook's React. A good pull request will be named such that you understand the purpose of the changes made. .

Objectives

Participants will be able to:

  • Create a branch within an existing GitHub repo on their laptop
  • Push that branch to GitHub
  • Create a pull request, merging that branch into master
  • Review a peer's pull request
  • Resolve simple conflicts when merging a pull request

Specific Things to Learn

  • Steps to create a new branch
  • Things to check when creating a new pull request

Supplemental Materials

Lesson

Things to Remember

  • If you mess up, you can usually undo what you just did. https://github.com/blog/2019-how-to-undo-almost-anything-with-git
  • When working on a team project, NEVER push to the GitHub master branch directly. It's best to never commit directly to master as well.
  • The best GitHub practices allow us to minimize chances for merge conflicts (this happens when multiple people worked on the same file).
  • When you do get a merge conflict, multiple people should sit down and resolve this either on GitHub or in VS Code.
  • In general, someone else should approve your pull requests to the master branch as to get an extra set of eyes.
  • Always pull from the shared project before working to make sure you have the most up-to-date version.

Guided Practice

  1. Fork a GitHub repo
    • Navigate to https://github.com/Techtonica/curriculum/
    • Click the button on the top right of the screen that says "fork"
    • Click the button next to "clone this repo"
    • On your command line, navigate to the folder where you keep your projects, and type git clone and press command+v to paste in the git repo you copied. It should look like this:
    git clone https://github.com/mygithubhandle/curriculum.git
    Press enter.
  2. Contribute to the project
    • Enter cd curriculum to navigate into your newly cloned repo.
    • Enter code . . Your VS Code editor should open to show the curriculum repo.
    • Open practice/apprentices.md. Add your name on it own line in the file. Press command+s to save.
  3. Commit and push your changes.
    • On your command line, enter git status. Copy the text practice/apprentices.md using your keyboard shortcut command+c.
    • Enter git diff practice/apprentices.md by pasting the file name using command+v again. This is a good habit to get into if you are trying to submit work in a shared project.
    • Try doing git diff again, but instead enter just git diff practice and press enter. You should get the same thing. If there were 2 files with changes in the practice folder, git diff practice would show the diffs of both files.
    • Enter git add practice/apprentices.md or git add practice. The second command works in this case because there's only one file in practice/ to worry about anyway.
    • Enter git commit -m "add my name" to commit with a message.
    • Enter git push origin master. You should see a message saying your remote fork, this repo's origin, was updated successfully.
  4. Make a Pull Request to Techtonica/curriculum.
    • Go to your GitHub account, and find your 'curriculum' repo. Click the green button that says 'compare/pull request'.
    • Make sure you are making a request to merge mygithubhandle/curriculum into Techtonica/curriculum/. If this were a real team project, you could briefly explain what you changed, why, and if there's anything else your team should know about this PR. In this exercise, you can skip it and just make the title your name or "add my name", and press 'create pull request'.
    • Navigate to the Techtonica/curriculum repo's 'pull requests' tab to see your PR has been added. Refresh your page to see whether more have have been made after yours.
  5. Make a Pull Request to your partnersGitHubHandle/curriculum master branch.
  6. Practice merging
    • Choose one pair of volunteers sitting next to each other. The first should go into their partner's PR in their own fork, click the "file changes" tab, and click the 'review button' and approve the PR. Ask that person to narrate what they are doing.
    • Have the other partner go into their approved PR and click 'merge'. Once there is a message saying it was successful, click 'delete branch'.
    • Ask everyone to navigate to Techtonica/curriculum/practice/students.md. The apprentice's name should now be in the master branch!
    • Ask everyone else to pair up and do the same, then switch who is reviewing and who is making the PR & merging.
    • Surprise! Everyone after this should have a merge conflict. Click on the grey "resolve conflicts" button and adjust things to preserve all the names on the list so far. Click 'commit merge'. If you return to the conversation and there are no more merge conflicts, go ahead and click 'merge', then 'delete branch'.
    • Look at Techtonica/curriculum/practice/apprentices.md again. You all just collaborated on this file!
  7. Practice pulling
    • Add Techtonica/curriculum as a remote
    • git pull techtonica master
    • Your command line may print that the merge was successful, but it is more likely that you have merge conflicts. The message will tell you which files to fix conflicts in, but of course it will be in practice/apprentices.md this time.
    • Navigate to that file, click 'their changes', then save.
    • Back in your command line, enter:
    git status
git add practice/apprentices.md
git commit -m "resolve merge conflicts"
git push origin master
    • Now your fork is up to date with the original Techtonica/curriculum repo. For the moment, at least.
  8. Adding a new remote repo(from atlassian.com)
    • Create a new connection to a remote repository. After adding a remote, you’ll be able to use as a convenient shortcut for in other Git commands. `
      • git remote add <name> <url>
    • Remove the connection to the remote repository called .
      • git remote rm <name> -Rename a remote connection.
      • git remote rename <old-name> <new-name>
    • The git remote command will list previously stored remote connections to other repositories.
      • git remote
    • Invoking git remote with the -v option will print the list of bookmarked repository names and additionally, the corresponding repository URL.
      • git remote -v.
    • This command fetches a copy of the master branch from the originating cloned repository, and merges it with the current branch you have checked out. You can use this to keep your branch up to date with master as you work.
      • git pull origin master -git pull will pull from the origin remote branch that you have checked out; then automatically merge it. For example, if you cloned your forked repo and are currently on the "test" branch, the command will pull from the test branch in your forked remote and merge it to your local "test" branch, in this example making it the same as git pull origin test.
    • If you want to keep the fork project updated with the main project you forked, the following steps need to be followed:
      • Clone the forked repository:
      • Add remote from original repository to the forked repository
        • cd into/cloned/fork-repo
        • git remote add upstream git://github.com/<ORIGINAL-DEV-USERNAME>/<REPO-YOU-FORKED-FROM>.git (you can name it anything; upstream is an example.)
      • Updating your fork from the main repo to keep up with their changes:
        • git pull upstream master

Challenge

Make another PR by checking out a new branch

  1. git pull techtonica master again. Fix any merge conflicts and commit.
  2. Enter git checkout -b middle-name to create a new branch.
  3. In practice/students.md, give yourself a cool nickname with quotes, ex: Margot "Danger" Tenenbaum
  4. git pull techtonica master again before pushing your new changes, just in case someone else made a commit in the time it took to do your work. (In real life, you will likely be working on a change for hours or days.)
  5. git status, add, commit, push, and make a PR for your middle-name branch to merge into the Techtonica/curriculum master branch.
  6. Ask someone to review your PR. This time, they should request changes with some bogus message, submit your review, and let you see it before resolving it and approving the PR after all.
  7. Fix any conflicts and merge the changes.
  8. Congrats, your cool nickname should be in the Techtonica/curriculum master branch!

Check for Understanding

  • Gather into small groups and discuss:
    • Why do you think forks and new branches would be good tools in a team project?
    • How do you keep your fork up-to-date with the shared project?
    • What is the first thing you should do before working on a issue/project?
    • What is the git command to create a new branch?
    • Discuss the importance of a good commit message.
    • What things should you check when creating a new pull request?
    • Describe how would you resolve merge conflicts?