Git, GitHub and Collaborative Development
Why colleges run this
Nobody teaches it and every recruiter checks it. Your students finish with a public portfolio repository they keep for life.
Course outcomes
CO1
Apply commits, branches and merges to manage a project's history
K3CO2
Resolve merge conflicts and explain what caused them
K4CO3
Conduct a pull-request review giving and responding to written feedback
K4CO4
Construct a public portfolio repository a recruiter can navigate
K3CO5
Write commit messages and documentation that explain intent, not mechanics
K3Modules tap a module for its theory & lab
Hours shown are the recommended 2-day format — module time scales to the duration you pick.
01Version control thinking4 h
Theory
Why history matters, repositories, commits, the staging area, good messages
Lab
Initialise, commit and inspect history on a starter project
Output
Repository with meaningful history
02Branching and merging4 h
Theory
Branches, merges, conflicts and their honest resolution
Lab
Deliberately create and resolve merge conflicts
Output
Merged feature branch
03GitHub collaboration4 h
Theory
Remotes, pull requests, code review etiquette, issues
Lab
Paired pull-request exchange with review comments
Output
Reviewed and merged pull request
04The public portfolio4 h
Theory
Profile READMEs, project documentation, licences, what recruiters look for
Lab
Build the personal portfolio repository
Output
Public portfolio repository
Every participant receives
Certificate of completion Course material LMS access Interview question bank Mock interview & viva practice Optional nasscom NSQF assessment