Pro Kit · e-book + tools27 filesAbout 3 hours to read

Use Git and GitHub with confidence, from your first commit to clean, reviewed pull requests

For university students, team leads and work teams: a 12-chapter e-book that follows one capstone team for 15 weeks, a practice pack of 12 guided exercises that run on your own computer, and the templates and workbook to run a team repository properly.

  • 12 guided exercises that build real Git repositories on your computer, including a ready-made merge conflict, a leaked fake secret, a fork to sync and a simulated team, each with a verify check and a model solution
  • A team working agreement, pull request and issue templates, a review checklist, a conflict record and a secret leak response form
  • A 16-sheet team workbook with self-assessment, PR and conflict logs, roadmap, RACI and a dashboard, plus a business-case calculator and readiness check
  • An integrity-first AI prompt pack (26 prompts), a 30-message library, a 10-case casebook and a 30-day practice plan

The Git and GitHub for Students and Teams Kit · Bodhih Pro Kits · 357 by Bodhih Training, trainers to 2,000+ companies since 2008.

Quick answer

How do I learn Git and GitHub for a team project?

Set up Git and two-factor authentication, then practise the core loop: small commits, short-lived branches, small reviewed pull requests and conflicts resolved by agreement. Protect main, keep secrets out with .gitignore, and use revert for pushed mistakes. The Git and GitHub for Students and Teams Kit from Bodhih Training gives exercises and templates for each step.

Want the full free guide first? Read How to use Git and GitHub for a team project, step by step.

Sound familiar?

You already feel the problem. Here is what it is costing you.

Zip files and lost work

Versions called final_v3_REAL.zip, a teammate's work overwritten, and nobody sure which copy is current.

Merge conflicts that feel like disasters

The terminal says CONFLICT the night before a demo, and someone 'fixes' it by deleting the other person's work.

Pull requests nobody reviews

Huge changes wait days, then get approved in minutes without anyone reading them.

Secrets and scary commands

A password in config.py, a forum answer that says reset --hard and push --force, and a team that no longer trusts its history.

Now imagine this

Picture the next few weeks with the kit open beside you.

Imagine week 13 of your project: a merge stops with a conflict, and instead of panic you open the five-step fix, ask the owner of the rule, run the tests and log it in twelve minutes.

As you open the practice pack tonight and run your first exercise, you will see Git's three areas on your own screen, and by the end of the week you will have resolved a real conflict and undone four mistakes safely.

Whether you start with the 15-minute quick start or the team working agreement, the dashboard fills in one Friday at a time, and on release day you tag a version that you have tested and can explain line by line.

What’s in the box

27 files that do the work for you

The e-book shows you how. The tools make it happen. Here is exactly what you download.

E-book

The Git and GitHub for Students and Teams Kit (e-book, PDF)

The guide: methods, worked examples, scripts and exercises

🔒
Cheat sheet

Start here: the kit map and 15-minute quick start

The whole job as a flow with the file to open at each step, a 15-minute quick start, your first hour and your first week.

🔒
Cheat sheet

Situation router: which files to open, in what order

Fourteen common situations, each with the files to open in order, plus the 15-minute quick start.

🔒
Spreadsheet

Git and GitHub team master workbook (16 sheets)

Settings, 0-4 self-assessment and gap plan, team roster, weekly log, pull request log, conflict log, roadmap, RACI, decision log, Tool notes, What changed, glossary, sources and a dashboard with four charts.

🔒
Spreadsheet

Business-case calculator: four cases with break-even week

Low, expected, high and do-nothing cases for adopting a Git workflow, in hours (and money if you want), with break-even week and a week-by-week chart.

🔒
Spreadsheet

Crosswalk and official sources register (US, Canada, UK, EU, Ireland, Australia, New Zealand)

Privacy law, student-record rules and code-ownership checks by market, with official URLs, plus a register of every source with its last-checked date.

🔒
Spreadsheet

Readiness check (go/no-go): team repository before a release

Twelve criteria with critical flags, evidence and a GO, GO WITH ACTIONS or NO-GO verdict by formula.

🔒
Fillable PDF

Team repository set-up checklist

Everything to set up before the first shared push: accounts, 2FA, repository, protection, templates, secrets and roles.

🔒
Fillable PDF

Pull request review checklist

A one-page checklist for author and reviewer: size, description, tests, secrets, accessibility, AI declaration and the decision.

🔒
Fillable PDF

Merge conflict resolution record

Records who decided what when a merge conflicts: files, both sides, the agreed result, the test run and the prevention.

🔒
Fillable PDF

Secret leak response form

Step-by-step response when a password, token or key reaches a repository: rotate first, then clean up, record and prevent.

🔒
Fillable PDF

Practice exercise checklists (12 exercises)

A printable checklist for each of the 12 practice-pack exercises, with space for what you learned.

🔒
Word template

Team working agreement and Git workflow procedure

A one-page, 12-rule agreement plus the branch, commit, review, secrets and AI conventions, ready to brand and sign.

🔒
Word template

Repository security and secrets procedure (starter)

A plain-English procedure for accounts, 2FA, access, secrets, personal data, leaks and offboarding in a team repository.

🔒
Word template

Sign-off memo: release or workflow approval (instructor or sponsor)

A one-page memo asking an instructor, client or manager to approve the team's workflow or release, with evidence and open actions.

🔒
Word template

Message library: 30 messages for Git teams

Ready-to-edit messages for kick-off, review requests, kind change requests, conflicts, bad pushes, leaked secrets, open source, releases and AI declarations.

🔒
Word template

Worked example pack: Sam's filled working agreement, review checklist and conflict record

The persona's completed versions of the three most-used templates, with numbers that match the workbook.

🔒
Word template

Scenario casebook: 10 cases with model answers

Ten realistic cases from the US, Canada, the UK, Ireland, Australia and New Zealand, student and work teams, with questions and model answers.

🔒
Word template

45-minute team briefing session plan and answer key

Run a 45-minute Git and GitHub briefing for your team or class: timings, live demo with the practice pack, discussion, the 14-question check and its answer key.

🔒
Word template

AI prompt pack: 26 prompts with human-review rules

Tool-agnostic prompts for learning Git, commit messages, conflicts, undo, reviews, open source, secrets and releases, each with what to paste and what to check.

🔒
Cheat sheet

Numbers that matter: the Git team KPI card

Twelve numbers a Git team runs on: definition, formula, where it lives in the workbook and what to do if it moves.

🔒
Cheat sheet

Correct at November 2026: Git and GitHub facts, rules and official sources

Every version-specific fact (versions, plans, limits, defaults) and the privacy crosswalk, each with its official source, dated.

🔒
Cheat sheet

Git command cheat sheet and undo decision card

The 40 commands students and teams use most, grouped by job, plus a decision card for undoing mistakes safely.

🔒
Calendar plan

30-day practice plan calendar (14-day core plus 16 days on your own project)

Thirty short evening sessions: the 14-day core with the practice pack, then 16 days applying it to your own repository. Import into Google, Outlook or Apple Calendar.

🔒
Import file

Task board: 30 practice tasks (CSV for Trello, Asana, Planner, Jira or Notion)

The 30-day plan as an importable task list with owner, status and done-when columns.

🔒
Import file

Knowledge check: 14 scenario questions (LMS-ready CSV)

Scenario questions with four options, the correct letter and an explanation; imports into Bodhih LMS or any LMS that takes CSV.

🔒
pack

Practice pack: 12 guided Git exercises, templates, CI project and portfolio site

Bash scripts that build real repositories (including a ready-made merge conflict), verify scripts, model solutions, a self-test, templates, a tested Python project with a GitHub Actions workflow and a GitHub Pages portfolio starter.

🔒
Inside the e-book

Chapter by chapter

Each chapter opens with a real situation, gives you a method and ends with something to do today, using the tools in your kit.

Format
PDF e-book + practice pack (ZIP) + XLSX + fillable PDF + DOCX + ICS + CSV
Files
27 files plus a one-click ZIP
E-book
87 pages
Works with
Git 2.28+ on Windows (Git Bash), macOS and Linux; GitHub; Excel, Google Sheets, Word, Google Docs, Acrobat; any LMS that imports CSV
Best for
Students, team leads, instructors and small work teams
  1. Why version control, and how Git thinks

    Snapshots, local work, checksums and the three areas that explain most of Git's behaviour.

  2. Install and configure Git

    Install Git, set your identity and default branch once, connect to GitHub with 2FA, SSH or a credential manager.

  3. Commits that tell the story

    One idea per commit, messages that say why, and a commit template the whole team uses.

  4. Branches and merging

    Branches as movable names, fast-forward and three-way merges, and when to merge or rebase.

  5. Resolving merge conflicts

    Read conflict markers, let the rule owner decide, test, record it, and prevent the painful ones.

  6. Remotes and GitHub repositories

    Clone, fetch, pull and push without forcing, set up a team repository, licences and privacy.

  7. Issues, pull requests and reviews

    Issues, pull requests, small changes, kind reviews and branch rules that protect main.

  8. Forks and open source

    Fork, sync from upstream, contribute to open source politely, and respect licences.

  9. .gitignore, secrets and safety

    .gitignore rules, secret scanning, push protection and the rotate-first leak response.

  10. Undoing mistakes safely

    restore, reset, revert, stash and the reflog, chosen by two questions: committed? pushed?

  11. Tags, releases, Pages and Actions

    Annotated tags, semantic versions, GitHub Actions tests on every pull request and a GitHub Pages portfolio.

  12. Team workflows, AI assistants and your practice plan

    Short-lived branches, a signed working agreement, integrity-first AI rules and a 30-day practice plan.

What you get

Not just reading. Tools you will actually open again.

Start here

  • Start here: the kit map and 15-minute quick start, with first hour, first week and 'brand it in five minutes'
  • Situation router: which files to open, in what order (14 situations)

Practice pack (runs on your computer)

  • Practice pack: 12 guided Git exercises that build real repositories, each with build, verify, a model solution and a checklist, plus a self-test
  • A ready-made merge conflict, a committed fake secret, a fork with an upstream, and a simulated team pushing branches
  • Templates: starter .gitignore, commit message template, pull request and issue templates, CONTRIBUTING, CODEOWNERS example, working agreement, AI use statement
  • ShelfShare mini: a small Python project with 11 tests and a GitHub Actions workflow; a GitHub Pages portfolio starter

Workbooks

  • Git and GitHub team master workbook (16 sheets): self-assessment, gap plan, roster, weekly log, PR log, conflict log, roadmap, RACI, decision log, Tool notes, What changed, glossary, sources, dashboard
  • Business-case calculator: four cases with break-even week
  • Crosswalk and official sources register (US, Canada, UK, EU, Ireland, Australia, New Zealand)
  • Readiness check (go/no-go): team repository before a release

Fillable forms

  • Team repository set-up checklist
  • Pull request review checklist
  • Merge conflict resolution record
  • Secret leak response form
  • Practice exercise checklists (12 exercises)

Word templates

  • Team working agreement and Git workflow procedure
  • Repository security and secrets procedure (starter)
  • Sign-off memo: release or workflow approval (instructor or sponsor)
  • Message library: 30 messages for Git teams
  • Worked example pack: Sam's filled working agreement, review checklist and conflict record
  • Scenario casebook: 10 cases with model answers
  • 45-minute team briefing session plan and answer key
  • AI prompt pack: 26 prompts with human-review rules

Cheat sheets

  • Git command cheat sheet and undo decision card
  • Numbers that matter: the Git team KPI card
  • Correct at November 2026: Git and GitHub facts, rules and official sources

Calendar, imports and training

  • 30-day practice plan calendar (14-day core plus 16 days on your own project)
  • Task board: 30 practice tasks (CSV for Trello, Asana, Planner, Jira or Notion)
  • Knowledge check: 14 scenario questions (LMS-ready CSV)

E-book

  • 12-chapter e-book (about 13,000 words, 36 figures including 5 real screenshots), following Sam's capstone team through 15 weeks
Outcomes

When you have worked through it, you will be able to…

Every outcome is practised with a worked example and a tool, not just described.

  • Set up Git and GitHub securely, with 2FA and the right authentication for your network
  • Commit, branch and merge with messages and names your team can read
  • Resolve merge conflicts calmly with the five-step fix, and prevent most of them
  • Run a team repository with small pull requests, real reviews and rules that protect main
  • Keep secrets out of Git and respond to a leak in the right order
  • Undo mistakes safely by choosing between restore, reset, revert and the reflog
  • Tag releases, run tests in GitHub Actions and publish a portfolio with GitHub Pages
  • Use AI assistants with Git within your institution's integrity rules
Measure it

Know your starting point. Prove your progress.

People who measure before and after improve faster and can show it. AssessAll, our sister assessment platform, has AI-graded assessments that pair with this kit. Take one now, work through the kit, then re-take it.

Read a page

A taste of Chapter 4

Week 4, Monday. Priya wanted to restyle the catalogue grid. Marcus was halfway through a database change that broke the app for an afternoon. Under the zip-file system, Priya would have had to wait, or work on a copy and merge it by hand. Sam drew two lines on the whiteboard, one straight and one curving away and back, and said: "From today, nobody works on main." What a branch is A branch is just a movable name that points at a commit. When you commit on a branch, the name moves forward to the new commit. Creating a branch is instant and cheap, so you can make one for every piece of work: git switch -c 12-search-by-author creates a branch and moves you onto it. git switch main takes you back. Your files change on disk to match whichever branch you are on, which is why Git asks you to commit or stash unfinished work before you switch.

From The Git and GitHub for Students and Teams Kit, Bodhih Training
Why this kit

The honest comparison

Free templates and typical adviceThis kit
PracticeRead-along tutorials with screenshots12 exercises that build real repositories on your computer, with verify checks and a self-test
Merge conflictsA paragraph on conflict markersA ready-made conflict, a five-step fix, a resolution record and a 'who decides' rule
Team workingSolo commands onlyWorking agreement, PR and review templates, RACI, roadmap and a team dashboard
Mistakes and safetyUndo commands without contextAn undo decision card by 'committed? pushed?', and a rotate-first secret leak response
Students and integrityNot mentionedInstitution rules first, public or private decision, integrity-first AI rules
Up to dateUndated screenshotsTool notes with official links and a 'facts last checked' date of 21 November 2026
Who it’s for

Made for you if…

  • University students starting a group or capstone project on GitHub
  • Team leads and teaching assistants who must get four or forty people working in one repository
  • Instructors who want a ready-made Git briefing, exercises and an LMS-ready knowledge check
  • Analysts and professionals moving scripts off a shared drive into a repository
  • Self-taught developers who use Git daily but avoid conflicts, undo and reviews
  • Learners in the US, Canada, the UK, Ireland and the EU, Australia, New Zealand and other English-speaking markets
Being honest

Probably not for you if…

  • Experienced engineers looking for Git internals, monorepo tooling or enterprise administration
  • Anyone wanting legal, privacy or academic-integrity rulings: the crosswalk points to official sources, it is not advice
  • Readers who want to use AI coding assistants at depth: Bodhih's Claude Code and AI Coding Assistants kit covers that; this kit covers Git and teamwork
Why Bodhih

Built by trainers, tested in real rooms.

Bodhih Training has designed and delivered corporate programmes since 2008. Bodhih Pro Kits package what works in those workshops into a guide plus the exact tools we use, so you can apply it the same day without a facilitator in the room.

2008Training organisations since
2,000+Companies served
200,000+Professionals trained
18,000+Programmes delivered
How it works

From here to using it in three steps

  1. STEP 1

    Tap Get the kit

    Name, email and country. UPI, card or netbanking in India; international cards everywhere else. No account to create.

  2. STEP 2

    Download instantly

    Your download page opens at once, with every file and a one-click ZIP. A permanent link lands in your inbox too.

  3. STEP 3

    Open the first tool

    Start with the quick-start chapter, then the main spreadsheet or planner. Most buyers use something from the kit the same day.

Ready when you are

Your next commit can be your best one

Open the practice pack, run the quick start and resolve your first real conflict today. Whether you begin alone tonight or with your team on Monday, the method and the files are ready.

$24one-time payment

Personal licence for the buyer's own use, and use with your own team, class or clients where the kit says so. Please don't share or resell the files. Team and company licences: solutions@bodhih.com.

What buyers say

No ratings yet. Only people who have bought this kit can rate it - every buyer gets a one-click rating link a couple of days after their purchase.

Questions buyers ask

The Git and GitHub for Students and Teams Kit: FAQs

Read the free guideAlready bought? Resend my link

Do I need to know how to code to use this kit?

No. You need to be able to open a terminal and type commands. The exercises use small text files and a tiny Python project; you never have to write code you do not understand, and every command is explained.

What is the difference between Git and GitHub?

Git is the version control tool that runs on your computer and keeps the history. GitHub is a hosting service built around Git that adds pull requests, reviews, issues, Actions and Pages. The kit teaches Git so it works with any host, and shows GitHub where courses and jobs use it.

How long does it take to learn Git for a team project?

The 15-minute quick start gets you configured and through a real merge conflict. The 14-day core plan works through all 12 exercises in short evening sessions, and days 15 to 30 apply each step to your own repository. How fast you become confident depends on how often you practise.

Does the practice pack need a GitHub account or internet?

No. The remotes in the exercises are folders on your computer, so everything works offline. You need Git 2.28 or newer, a bash shell (Terminal on macOS and Linux, Git Bash on Windows) and Python 3.9 or newer for two exercises. Optional steps repeat the flow on GitHub.

Can I use AI tools like ChatGPT or GitHub Copilot with Git for coursework?

Only as your course allows. The kit puts your institution's rules first and gives 26 prompts with an integrity-first rule set: the AI explains, people decide, nothing secret or personal is pasted in, and every author can explain every line. It also summarises measured studies that disagree on speed gains.

How do I fix a merge conflict in Git?

Read both sides between the conflict markers, let the owner of the rule decide, write the agreed result, delete the marker lines, run the tests, then git add and git commit. git merge --abort takes you back if you get lost. Exercise 05 gives you a ready-made conflict to practise on.

I pushed a password or API key to GitHub. What do I do first?

Revoke and replace (rotate) it at the provider first, because deleting the file does not make the old value safe. Then move secrets to an ignored .env file, commit .gitignore and .env.example, tell your instructor or manager, and record it. The Secret leak response form lists the order.

Can I use this with my team, class or students?

Yes, within your own team, class or organisation under the personal licence: run the briefing, share the working agreement you adapted and import the knowledge check into your LMS. Company, department and multi-site licences are available from solutions@bodhih.com.

Does it work in my country?

Git works the same everywhere. What changes is privacy law for personal data, student-record rules and who owns the code you write. The crosswalk maps these for the US, Canada, the UK, the EU, Ireland, Australia and New Zealand with official sources, dated November 2026. Check locally before acting.

How do I measure my starting point?

Score the 12 practices in the workbook's self-assessment. If you want an outside measure of related skills, AssessAll offers a Code Review Assessment for Software Engineering Teams, Pseudo-code and Programming Logic: Basics, and Study Skills and Learning Strategies.

How do I make the practice stick after the 30 days?

Book the sessions in your calendar and tie each one to a cue, such as 'after dinner on weekdays, one exercise'. Jobulary's article on if-then plans that make habits stick explains the method; the kit's task board and weekly log keep you honest.

Is this kit affiliated with GitHub or Microsoft?

No. Not affiliated with or endorsed by GitHub, Inc., Microsoft, the Git project or any university named; product names are used descriptively. Plans, limits and menus change, so every version-specific fact sits in the Tool notes sheet with its official link and the date it was checked.

How much does The Git and GitHub for Students and Teams Kit cost?

₹799 including 18% GST for buyers in India, or $24 for buyers outside India. One-time payment, no subscription, with an automatic invoice.

How do I get the files after paying?

Instantly. Your download page opens the moment payment succeeds, and a permanent download link is emailed to you. Download each file separately or everything in one ZIP.

What software do I need?

Any of the usual tools: Excel or Google Sheets for spreadsheets, Word or Google Docs for templates, Adobe Acrobat Reader, Preview, Xodo or GoodNotes for the fillable PDFs, and Google, Outlook or Apple Calendar for the calendar plan.

Can I get a refund?

Because it is a digital download, kits are not refundable once downloaded. We always refund a duplicate charge or a failed delivery, and if a file is corrupted and we cannot fix it within 3 working days. Full terms: bodhih.org/refunds.

Can my company buy this for a team?

Yes. Team and company licences, and workshops on this topic run by Bodhih Training, are available. Write to solutions@bodhih.com or call +91 99000 11601.

$24