STR Coding Club logo STR Coding ClubLearn to code, together
Club Projects

How to Run a Git Group Project at Your Coding Club

Three people edit the same Python file, someone emails a zip called final_v3_REAL.zip, and by week two nobody knows which version runs.

Four students around two laptops in a classroom, one pointing at a projector screen showing a list of code changes

Three people edit the same Python file, someone emails a zip called final_v3_REAL.zip, and by week two nobody knows which version runs. That is how most coding club projects fall apart, and it is why I now start every Git group project with a 45-minute setup session before anyone writes a line of game logic.

This article is the plan I use with mixed groups at our club: absolute beginners next to students who already push code every week. It covers the setup, the small set of commands beginners actually need, how to split work so conflicts stay rare, and what to do when a merge goes wrong in front of everyone.

Why a Git group project beats shared folders

A shared drive feels simpler, but it hides the problem until it is too late. Two members open the same file, both save, and one person's hour of work disappears without a trace. Git does not stop people editing the same file, but it notices, tells you exactly which lines clash, and keeps every earlier version so nothing is ever truly lost.

For a club there is a teaching bonus. Every commit message is a tiny written record of what someone did and why. When I review a group's history at the end of a session, I can see who is stuck, who is quietly doing everything, and who needs a nudge, without asking anyone to justify themselves out loud.

The 45 minute setup session

Run this as its own session. Mixing setup with the first coding sprint means the beginners fall behind on day one and never catch up.

  1. Accounts and installs (15 minutes). Everyone creates an account on a Git hosting service and installs Git. Have two experienced members walk the room. Windows machines take longest, so start them first.
  2. Identity (5 minutes). Each person sets their name and email with git config. Skip this and the history fills with commits from "unknown", which ruins the review later.
  3. Clone the starter repository (10 minutes). The organiser creates the repository beforehand with a README, a .gitignore for Python, and a working main.py that prints one line. Everyone clones it and runs it. A project that runs on day one is worth more than any slide.
  4. First commit (15 minutes). Each member adds their name to a CONTRIBUTORS.txt file, commits, and pushes. Yes, this creates deliberate conflicts. That is the point. You resolve the first one together on the projector while everyone watches.

If you have never planned the full arc of a club build, our guide to planning a six week coding club project fits around this setup session neatly as week zero.

Six commands are enough for beginners

Experienced members will want to show off rebase, stash and cherry-pick. Ask them not to. Beginners need six commands, and they need them to become boring.

CommandWhat it does in plain wordsWhen to run it
git pullGet everyone else's latest workEvery time you sit down
git statusShow what you changedWhenever you feel unsure
git addPick which changes to saveBefore each commit
git commit -mSave a snapshot with a messageAfter each small working step
git pushSend your snapshots to the shared copyBefore you leave
git switch -cStart a new branch for your taskWhen you pick up a new card

Print this table and tape it next to every machine. I mean physically print it. A sheet of paper does not get lost behind six browser tabs.

Split the work so conflicts stay rare

Most merge pain comes from poor task splitting, not from Git. The fix is structural: give each person their own file whenever possible.

For a text adventure, for example, one member writes rooms.py, another writes items.py, a third writes the command parser, and main.py only imports and connects them. The Python text adventure group project already uses this layout, which is one reason it works so well for a first Git experience.

Use a simple board with three columns: To do, Doing, Done. Each card names one file or function and one owner. A good card takes a beginner 30 to 60 minutes. If a card sits in Doing for two sessions, it was too big, so split it.

Pair beginners with a stronger member for their first pull request. The stronger member reviews but never types. That rule is hard to enforce and worth every reminder, because a beginner who watches someone else fix their branch learns almost nothing.

Push back on "everyone commits straight to main"

Some club leaders tell beginners to skip branches entirely and commit to main, on the grounds that branches are "too advanced". I used to do this. I stopped after a term where main was broken for eleven days because one push half-finished a function and nobody could run the game.

The better approach is one branch per card, merged through a pull request that someone else approves. It adds about two minutes per task. In return main always runs, so anyone arriving late can pull and play the current build immediately. That working build is what keeps beginners motivated, and it costs almost nothing.

The one exception is the very first session. Committing to main for CONTRIBUTORS.txt is fine because the conflicts are harmless and teach the idea quickly.

When a merge conflict happens in front of everyone

It will happen, usually ten minutes before the session ends. Treat it as a lesson, not an accident.

  • Put the conflicted file on the projector and point out the three markers: the start of your version, the divider, and the end of their version.
  • Ask the two people involved which lines should survive. Often the answer is both, in a sensible order.
  • Delete the markers, run the program, then commit. Running before committing is the step people skip.

Keep a "conflict of the week" slot of five minutes. After three or four weeks, members start resolving their own without calling anyone over, which is the moment you know the habit has landed. For broader ideas on mixed ability builds, see more club project ideas.

Frequently asked questions

How old should students be to use Git in a club?

Most students from about 12 upward handle the six basic commands fine with a printed cheat sheet. Younger groups do better with a graphical client or the editor's built-in Git panel. The concepts matter more than the command line.

Should beginners learn Git before they learn Python?

No. Let them write a few small programs first so they have something worth saving. Introduce Git at the start of their first shared project, when the need is obvious and the reward is immediate.

What is the easiest way to undo a bad commit?

For beginners, git revert is the safest choice because it adds a new commit that reverses the old one instead of rewriting history. Everyone else's copy stays consistent. Save reset for experienced members working on their own branches.

IA
Imogen Achebe

Imogen started a coding club at her school and now trains volunteer mentors. She writes about first steps in coding and projects that work for groups of mixed ability.

More posts by Imogen

More in Club Projects

01doorganico 084goad 3hot8 4465456 after5internprogram ahandfulofblessings ahmadpc ahomcybersecurity allodialresources annodex antiquesandperiodcollectibles aotc asianworldkashmir beedlectrics bloggertemplatefree bluefeatheragency bodyweightsolution campaign08blog carfixadvisor catstreetcollective cbstvsports cnfanspurchasing committeeof500yearsofdignityandresistance covertopsdjs cs-kaiyuangame cuestacomunicaciontotal cxoutlet dancebetgame deskgearhub destinyvillastay detectmagazine di33 diamondsteelbuildings donmo dyanadropship emarsysfinance emimattl escapechan eskitarih evautoplay everythingweddings-orlando farmzone feedviewerapp foxstudiosscratch gamevui123 gleasongrade greetingsday hacklabasu haskell iw-kaiyun jagoanproperti jilidskripsi joltbusinessfinance juegodepokergratis juegospucca kaeru-festival latestmehndidesigns lestanzediottaviano litemagazines localcommunityhero lustrsazan mariashebets menswheels newwebstechs1 nikkit ootheday oxigenvpn plurfitness prefetial probudgetcarpetcleaning psychicmrsmartin pyaten qvantor rejoignezlogis rexzbot riselayouts ruchin rwxqsgd5 sakaltime shibiaowang shop-bot skrtips spotlesshaven tetapatrium topselller uneplanteartificielle vipertechcr webtech1223411 wo-kygaming yamaha-mekar yeknava yoybuysheets zenunwa yamaha-mekar jilidskripsi ankertoto ankertoto ankertoto