Collaborative Code Sharing

Active learning works well for collaborative coding because version control disciplines like pull requests and code review are inherently social. Students need to practice coordinating edits, explaining decisions, and resolving feedback in real time to understand how distributed teams ship reliable software.

• 9th Grade
• Computer Science
• 4 activities
• 20 min–45 min

Learning Objectives

1. Design a process for a small team to contribute code to a shared repository using version control.
2. Analyze the benefits of using version control for tracking individual contributions and identifying merge conflicts.
3. Critique code contributions from team members, providing constructive feedback before merging.
4. Synthesize individual code segments into a cohesive project through effective merging strategies.

Collaborative Problem-Solving

⏱ 45 min·Small Groups

Collaborative Lab: Shared Repository Workflow

Groups of three share a repository. Each student is assigned to edit a different function in the same file, commit their changes, and push to a shared remote. The group then pulls all changes and discusses what happened when edits overlapped, practicing the sequence of pull-before-push as a coordination habit.

Prepare & details

Explain how sharing code effectively contributes to a team project.

Facilitation Tip: During the Collaborative Lab, walk the room with a live repo projected on the board so students see branches and merges in real time.

Setup: Groups at tables with problem materials

Materials: Problem packet, Role cards (facilitator, recorder, timekeeper, reporter), Problem-solving protocol sheet, Solution evaluation rubric

• Apply
• Analyze
• Evaluate
• Create
• Relationship Skills
• Decision-Making
• Self-Management

Think-Pair-Share

⏱ 20 min·Pairs

Think-Pair-Share: What Makes a Good Pull Request?

Show students two pull request descriptions for the same code change -- one vague ('fixed bug'), one specific ('fixed null pointer exception in login when username field is empty'). Partners discuss which is more useful and why. Class builds a list of criteria for effective pull request descriptions.

Prepare & details

Design a process for team members to contribute code to a shared repository.

Facilitation Tip: In the Think-Pair-Share, prompt pairs to compare a vague commit message with a concrete one before sharing with the whole class.

Setup: Standard classroom seating; students turn to a neighbor

Materials: Discussion prompt (projected or printed), Optional: recording sheet for pairs

• Understand
• Apply
• Analyze
• Self-Awareness
• Relationship Skills

Round Robin

⏱ 40 min·Pairs

Code Review Round Robin

Each student submits a short code snippet (10-15 lines) to a shared folder. Students rotate to review a peer's code, leaving at least one positive observation and one specific suggestion for improvement as comments. After two rounds, students revise their code based on feedback received.

Prepare & details

Analyze the benefits of using version control for tracking individual contributions.

Facilitation Tip: For the Code Review Round Robin, provide a single PR template so reviewers focus on structure rather than format.

Setup: Chairs in a circle or small group clusters

Materials: Discussion prompt, Speaking object (optional, e.g., talking stick), Recording sheet

• Remember
• Understand
• Analyze
• Relationship Skills
• Self-Management

Gallery Walk

⏱ 25 min·Small Groups

Gallery Walk: Contribution Tracking

Display a repository's git log history (anonymized) on four poster sheets. Groups analyze the commit history and answer: Who contributed most? Are commit messages clear? Can you tell what the project does from the history? Groups report their analysis and class discusses what a healthy contribution history looks like.

Prepare & details

Explain how sharing code effectively contributes to a team project.

Setup: Wall space or tables arranged around room perimeter

Materials: Large paper/poster boards, Markers, Sticky notes for feedback

• Understand
• Apply
• Analyze
• Create
• Relationship Skills
• Social Awareness

Teaching This Topic

Teachers should avoid live-coding the entire PR workflow; instead, narrate each step while students perform it on their own machines. Emphasize that good version control is a habit, not a one-time lesson. Research shows that students benefit from seeing both successful and failed merges, so deliberately seed minor conflicts to build diagnostic confidence.

What to Expect

Students will demonstrate the ability to fork a branch, make focused commits, open a pull request, review peers’ work, and merge changes without losing contributions. They will articulate why clear commit messages, small PRs, and constructive reviews matter in professional workflows.

Watch Out for These Misconceptions

Common Misconception

During the Collaborative Lab: Shared Repository Workflow, watch for students who try to push directly to main or who create only one branch for the whole team.

What to Teach Instead

Use the lab’s step-by-step checklist to redirect teams: insist on branching from main, making small commits, and opening PRs before merging. Show them how a shared branch without PRs can overwrite work.

Common Misconception

During the Think-Pair-Share: What Makes a Good Pull Request?, watch for students who believe a PR’s only purpose is to fix errors.

What to Teach Instead

Use the provided PR rubric during the pair discussion: require reviewers to note at least one positive observation about code readability or design, not just bugs. Bring examples of PRs that improved maintainability.

Common Misconception

During the Gallery Walk: Contribution Tracking, watch for students who assume any overlap in a file will cause a conflict.

What to Teach Instead

During the walk, point to specific commits that edited separate lines in the same file and show the clean merge output. Ask students to predict when Git will auto-merge versus when it will flag a conflict line.

Assessment Ideas

Quick Check

After the Collaborative Lab: Shared Repository Workflow, present students with a scenario where two students’ changes were lost during a direct push to main. Ask students to identify the cause (no branching, no PR) and suggest one step they could have taken to prevent the loss.

Peer Assessment

During the Code Review Round Robin, have students work in pairs on a small coding task, each making separate commits. After completing their work, they create a pull request for their partner to review. The reviewer checks for clear commit messages, logical code structure, and adherence to requirements, providing written feedback on the PR.

Exit Ticket

After the Think-Pair-Share: What Makes a Good Pull Request?, ask students to write down three key benefits of version control for team projects. Then, have them describe one potential challenge they might face when merging code from a teammate and how they would address it.

Extensions & Scaffolding

• Challenge: Ask early finishers to refactor a teammate’s PR into smaller, more focused commits and explain the benefit in a comment.
• Scaffolding: Provide a partially completed PR template with example questions to guide reviewers who feel unsure what to write.
• Deeper exploration: Invite students to research and present one advanced Git feature like rebasing or squashing that can improve shared workflows.

Key Vocabulary

Repository	A central storage location for a project's files and their version history. In this context, it's where the team's shared code lives.
Commit	A snapshot of changes made to the code at a specific point in time. Each commit is a record of what was changed and why.
Branch	A parallel line of development created from the main codebase. This allows developers to work on new features or fixes without affecting the stable version.
Merge	The process of combining changes from one branch into another. This integrates new code into the main project or another feature branch.
Pull Request	A formal request to merge code from one branch into another, typically used to initiate code review and discussion before integration.