Git Commit Relay Race

Transform learning Git collaboration into an engaging team competition. This interactive workshop format and live scoreboard system tracks commit activity in real-time as teams race to build Streamlit dashboards, creating excitement around version control best practices.

Overview

Developed for large retreat workshops, this project creates a competitive yet educational environment where teams of 3-5 participants learn collaborative software development through hands-on practice. The live scoreboard, displayed prominently at the front of the room, tracks each team’s Git commits as they work through structured rounds with time limits.

Features

• Real-time commit tracking: Scoreboard updates live as teams push commits
• Team rankings: Dynamic leaderboard showing progress
• Visual engagement: Large display creates energy and excitement
• GitHub integration: Connects to team repositories automatically
• Instructor dashboard: Monitor all teams’ progress simultaneously

Workshop Format

Team Structure:

• 3-5 members per team
• Mixed skill levels encouraged
• Each member takes turns contributing
• Roles rotate through rounds

Competition Rounds: Teams progress through timed rounds:

1. Planning round: Design dashboard features and assign tasks
2. Sprint rounds: Implement features with rapid iteration
3. Integration round: Merge branches and resolve conflicts
4. Presentation round: Demo completed dashboards

How the Scoreboard Works

Setup

# Clone the repository
git clone https://github.com/ibehave-ibots/Git-Commit-Relay-Race.git
cd Git-Commit-Relay-Race

# Install dependencies
pixi install

# Configure team repositories
# Edit config.yaml with team GitHub repository URLs

# Launch scoreboard
pixi run scoreboard

Live Tracking

The scoreboard monitors configured GitHub repositories and:

1. Polls repositories at regular intervals
2. Counts new commits since workshop start
3. Updates team rankings dynamically
4. Displays commit messages and authors
5. Shows visual progress indicators

Educational Objectives

Git Collaboration Skills

Version Control Concepts:

• Atomic commits with clear messages
• Branch creation and management
• Pull requests and code review
• Merge conflict resolution
• Repository synchronization

Team Workflow:

• Feature branch workflow
• Code review practices
• Continuous integration awareness
• Communication through Git messages

Software Development Practices

Agile Methodology:

• Sprint planning and time-boxing
• Iterative development
• Stand-up style check-ins
• Retrospective discussions

Team Coordination:

• Task distribution and parallelization
• Dependency management
• Integration strategies
• Documentation practices

Learning Outcomes

Participants Learn:

1. Git fundamentals: Commit, push, pull, branch, merge
2. Collaboration workflows: Feature branches, pull requests, code review
3. Team communication: Through commits, issues, and documentation
4. Time management: Working under sprint time constraints
5. Conflict resolution: Both technical (merge conflicts) and interpersonal

Observed Benefits:

• Increased comfort with Git commands
• Better understanding of branching strategies
• Improved commit message quality
• Enhanced team communication
• Practical experience with real workflows

Facilitation Tips

Pre-Workshop:

• Create template repository with starter code
• Configure scoreboard with team repo URLs
• Test GitHub API access
• Prepare backup internet connection

During Workshop:

• Display scoreboard prominently on projector
• Announce round transitions clearly
• Celebrate team achievements as commits appear
• Provide Git help stations for technical issues

Post-Workshop:

• Share final rankings and statistics
• Conduct group retrospective
• Distribute resources for continued learning
• Collect feedback on format

Challenge Structure

Example Challenge: Streamlit Dashboard

Teams build a data visualization dashboard with:

Required Features:

• Data upload functionality
• Multiple visualization types
• Interactive filtering
• Custom styling
• Documentation

Scoring Criteria:

• Number of commits (primary metric)
• Feature completion
• Code quality
• Presentation effectiveness

Sample Round Schedule

Round 1 (15 min): Setup & Planning

• Create repository from template
• Set up development environment
• Plan features and assign tasks
• Make initial commits

Round 2 (30 min): Feature Development

• Implement core functionality
• Create feature branches
• Regular commits to track progress
• First integration attempts

Round 3 (20 min): Integration & Polish

• Merge feature branches
• Resolve conflicts
• Add documentation
• Final testing

Round 4 (15 min): Presentations

• Demo dashboards to all participants
• Share lessons learned
• Discuss Git challenges encountered

Impact and Results

Workshop Feedback:

• High engagement and energy levels
• Better retention of Git concepts
• Increased confidence with version control
• Positive peer learning experiences

Typical Outcomes:

• 50-100+ commits per team in 90 minutes
• All participants make multiple contributions
• Most teams successfully merge branches
• Strong understanding of collaborative workflows

Success Stories

Retreat Workshop Results:

• 40+ participants across 8 teams
• Over 500 total commits in 2 hours
• 100% participant engagement
• Immediate application of Git skills in subsequent projects
• Requests for repeat sessions

The competitive element combined with practical skill-building creates memorable learning experiences that stick with participants long after the workshop ends.