This is a Test Repo for learning about Git & Pair Programming
For pair programming “collaboration” with GitHub
- Person A forks the Lambda School repository.
- Person A adds person B as a Collaborator.
- Person B accepts invite.
- Both clone person A’s repository to their computers, for example:
$ git clone clone https://github.com/Person-A/Git-Foo.git Cloning into 'Git-Foo'... remote: Counting objects: 330, done. remote: Compressing objects: 100% (138/138), done. remote: Total 330 (delta 83), reused 171 (delta 56), pack-reused 124 Receiving objects: 100% (330/330), 1.31 MiB | 1.25 MiB/s, done. Resolving deltas: 100% (126/126), done.
- Work together, switch coding roles every half hour.
- Upon the first switch*, save all changes, and commit them in your local Git repository
- Push the commits to person A's GitHub repository
- Make a Pull Request to Lambda School from person A's GitHub repository.
- Person B pulls in the commits from Person A's GitHub repository.
- Push and pull changes as you switch.
- Commit often!
- Attend the end of day stand up meeting.
* You are welcome to make a Pull Request upon the first commit of any change you make to the project. While a Pull Request is "open" any subsequent commits which get pushed to your GitHub repository will be automatically added to the open PR.
Teaching Assistant's Afternoon Project Time Checklist
- Drop link to Zoom created with section Zoom account
- Add other section TAs as cohosts
- Announce project and review README
- Review how to fork and add a collaborator
- Review pair programming best practices
- One student drives, one types
- Switch every 30 minutes
- On every switch, push and pull all changes
- Create breakout sessions to assign pairs
- TAs use the Zoom Breakout rooms to drop in and help groups with questions
- Send switch reminders every 30 minutes (on the half hour)
Add Your name to the list Below
- Tai the Thai
- Ryan Hamblin