Performed by Section Lead or designated PM in each section each afternoon:
- Drop link to Zoom created with section Zoom account.
- Add other section PMs as co-hosts.
- Announce the project and review the README with the class.
- Review how to fork and add a collaborator to the forked repository.
-
Person A forks the Lambda School repository.
-
Person A adds person B as a Collaborator.
-
Person B accepts invite. The invite will be e-mailed to the e-mail account person B used to register with GitHub
-
Both clone person A’s repository:
git clone {person A's URL}. For example:
-
$ git clone https://github.com/mixelpixel/Precourse.git
Cloning into 'Precourse'...
remote: Counting objects: 36, done.
remote: Compressing objects: 100% (35/35), done.
remote: Total 36 (delta 8), reused 1 (delta 0), pack-reused 0
Unpacking objects: 100% (36/36), done.
$ cd Precourse/
$ git remote -v
origin https://github.com/mixelpixel/Precourse.git (fetch)
origin https://github.com/mixelpixel/Precourse.git (push)- Review pair programming best practices.
-
One student "drives" (does the typing), and the other "navigates."
-
Make Git commits often.
-
Switch roles every 30 minutes.
-
Upon the first switch, make a Pull Request to Lambda School.
-
With every switch, push and pull all changes. They will get added to the Pull Request automatically.
-
- Create breakout sessions to randomly assign pairs.
- PMs use the breakout rooms to drop in and help groups with questions.
- Send switch reminders every 30 minutes (on the half hour).
- PMs leave feedback on students' Pull Requests: https://github.com/LambdaSchool/Code-Review-Checklist