Find file History
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.

title type duration creator
Github for Teams
name city
Robby Grodin

Github for Teams


We're going to use the skills covered in the earlier lesson to practice interacting with a Github repository. By the end of this lab, you will have practiced merging Pull Requests, resolving Merge Conflicts, and maintaining Forks. These skills will enable you to effectively work as a team using Github as your source control tool. At the end of each part, make sure you switch roles and re-do the exercise. This was each partner will get to practice the skills covered.

Make sure you have a strong handle on the topics covered in this lab. They may feel awkward at first, but will become more meaningful over time. As you begin to work on this week's Kaggle project, as well as your final project, having an effective collaboration workflow will make everything much easier.

Instructor's Note: If you yourself have personal work experience with Git, I would suggest removing the next section and giving your own experience. This is here as a placeholder, in case Git is new to you.

As a Data Scientist in a technical environment, it is almost guaranteed that you will rely on Git or a similar source control system. At Wayfair, Git and GitLab (an alternative to GitHub) are used for everything from storing our source code, allowing easy collaboration, powering external codebase search tools, keeping code easily accessible for deployment, and documenting a project's progress. Some projects have hundreds of collaborators, some only have one, but all are stored in our Git repositories.

Note: This is a pair programming exercise.


At the end of this lab, you should have multiple repositories, each with merged Pull Requests.


Part 1

Merging Pull Requests

Partner 1:

  • Create a GitHub repository
  • Create a folder named "Pong"
  • Add two files named "" and ""
  • In the "" file, define a Paddle class with an empty main method
  • Commit and Push your changes to GitHub

Partner 2:

  • Fork and Clone the new GitHub repository
  • Add member variables to the Ball class to indicate X and Y coordinates
  • Add a new file named ""
  • Commit your changes and submit a pull request back to Partner 1

Partner 1:

  • Review and accept the Pull Request

#Now switch roles and do Part 1 again!#

Part 2

Syncing a Fork

Both Partners:

Partner 2:

  • Use the technique described in the documentation to sync your fork of Partner 1's GitHub repository.

Partner 1:

  • Create a new Fork of Partner 2's version of the GitHub repo
  • Edit the "" file to import both Paddle and Ball classes
  • Push your commit to Github and open a Pull Request

Partner 2:

  • Review and accept the Pull Request

#Now switch roles and do Part 2 again!#

Part 3

Merge Conflicts

Partner 1:

  • Edit the main method in "" to print "Hello World!"
  • Commit and push your code to your repository

Partner 2:

  • Edit the main method in your local copy of "" to print "Goodbye Cruel World!"
  • Commit and push your code to Partner 1's repository

Partner 1:

  • Create a Pull Request for your code
  • Review and Accept your Pull Request

Partner 2:

  • Create a Pull Request for your code. Note: You should have a merge conflict.
  • Edit the Merge conflict and successfully merge in your code

Now switch roles and do Part 2 again!


If you've mastered the exercises above, here are some bonus exercises you can try.

  • Create ten branches that all edit the same file, and then merge them all together
  • Create a fork of a fork of a fork, and attempt to push a commit all the way back up to the original repository
  • Merge your group with another group and try all of the above with 4 contributors instead of 2
  • Discuss the implications of each of the different Git workflows described in the earlier lesson

Additional Resources