Start Module 1
Create one shared repository from the Module 1 template and open it in RStudio.
Before you begin
Make sure every person in your group has completed the step-by-step setup and accepted the invitation to the dsep-ethz GitHub organization.
Check your membership in GitHub organization settings. If you cannot see dsep-ethz, ask Jory or Niál for help.
Choose one repository creator
Create one repository per pair, not one per person. Decide who will create it; the other person will join as a collaborator.
Use the Module 1 template
- Sign in to the GitHub account that joined the course organization.
- Open the Module 1 template.
- Select Use this template, then Create a new repository.
Name and create the repository
- Set the Owner to
dsep-ethz. - Name it
module1-lastname-lastname, replacing the example with every group member’s last name. - Use lowercase letters and hyphens, for example
module1-smith-garcia. - Choose Private, leave Include all branches unselected, and select Create repository.
Add collaborators
- Open Settings > Collaborators and teams in the new repository.
- Select Add people and invite every group member who did not create the repository.
- Add Jory Griffith, Niál Perry, and Millie Chapman using the GitHub usernames provided in class.
- Give collaborators Write access unless GitHub already grants access through the organization.
Each invited group member should accept the invitation before anyone begins editing.
Clone the repository in RStudio
- On GitHub, select Code, choose HTTPS, and copy the repository URL.
- In RStudio, select File > New Project > Version Control > Git.
- Paste the URL, choose where to store the project, and select Create Project.
- Confirm that
module1.qmd,README.md, and the Git pane are visible.
Every group member should clone the same shared repository to their own computer.
Test the shared workflow
- Choose a driver and navigator. Only the driver edits.
- Add all group members’ names to
README.md. - Save, commit, and push the change.
- On the other computer, pull and confirm that the change appears.
- Switch roles before beginning Module 1.
Before starting Module 1
- There is exactly one repository for your pair or group.
- It belongs to
dsep-ethzand includes every group member’s last name. - All group members, Jory, Niál, and Millie have access.
- Every group member can pull and push.
- The group names appear in
README.mdon GitHub.
Why pair programming?
Pair programming makes the reasoning behind the code visible. The driver practices explaining decisions while the navigator asks questions, catches mistakes, and keeps the larger goal in view. Switching roles helps everyone understand the full workflow, reduces the chance that one person becomes the only expert, and builds the shared Git habits needed to work together confidently.