Join the mission to spread the knowledge of git.
GitSetGo teaches git the only way it sticks — by making people run the commands. Branch, merge, rebase, resolve a conflict, recover from a mistake. Colleges and organisations sign a short MOU with us, their people play through the game, and everyone who finishes claims a verified certificate issued under that MOU.
Already a partner? Sign in to your dashboard.
Four steps from application to certificates
- 1
Apply
Tell us who you are, who the point of contact is, and roughly how many people you expect to take part. We review new applications within two working days.
- 2
Sign the MOU
We send a short memorandum of understanding covering what each side does — we issue the certificates, you get the programme in front of your learners.
- 3
Get your organisation code
Once the signed MOU is back we issue a code that belongs to your institution and open your dashboard.
- 4
Learners claim certificates
A learner finishes the game, enters your organisation code, and their certificate is issued under your MOU — and shows up in your dashboard.
Pick the track that fits your organisation
The programme runs the same way on both tracks — the MOU, the organisation code, the dashboard. What differs is how certification and certificate branding are covered.
Educational institutions
- Certification is free under the MOU. Every student your MOU covers earns a verified certificate at no cost to the institution or the student.
- College branding on certificates is a paid add-on.Want your institution's name and identity on the certificate itself, alongside GitSetGo's? That runs on a branded campaign we set up for you — priced when we prepare your MOU.
- Eligible for the public institution leaderboard, if you choose to opt in.
Corporates
- Certification and branding are both paid.Your cohort — new joiners, an intern batch, a team upskilling — certifies on branded certificates carrying your company's identity.
- Volume discounts, no minimum. Pricing scales with cohort size, and there is no floor — certify three engineers or three hundred.
- The same dashboard and CSV reporting as institutions, scoped to your cohort.
You pick the track on the application form; the MOU we send matches it. Not sure which fits? Apply anyway and say so in the notes — we will sort it out with you.
Certificates for your learners, and the paperwork to prove it
Verified certificates for your learners
Every learner covered by your MOU gets a certificate with a unique number they can verify and put on a CV.
A dashboard of who actually certified
Names, email addresses, the level they reached, the certificate number and the date it was issued. Not an aggregate — the actual list.
CSV export
Export the same list for your placement cell, NAAC or NBA file, or an internal report, without asking us for it.
An onboarding checklist
The handful of things that decide turnout — the launch announcement, the posters, naming an internal owner — tracked in one place so nothing quietly stalls.
Certificate branding options
Put your organisation’s name and identity on the certificate itself, alongside GitSetGo’s — a branded campaign we set up as part of your MOU.
Only the things that decide turnout
- Name an owner. One person at your end who answers email and knows the programme is running.
- Announce it to your people. A mail or LMS broadcast with the organisation code, sent to the departments in scope.
- Put the posters up. We send the artwork; labs and notice boards do the rest.
These are the same items that appear as your onboarding checklist in the dashboard, so both sides can see what is done and what is still open.