TechnologyThe ProfessorBeginner
Sharing Code on GitHub, a free technology course on Tomo

Sharing Code on GitHub

Learn to grab open-source projects, publish your own work to the cloud, and collaborate with other developers. Master the core rhythm of downloading, saving snapshots, and sharing repositories without getting lost in technical jargon.

Like Duolingo, but for Sharing Code on GitHub. Tomo turns the whole topic into a game you play five minutes a day, until it actually sticks.

A short one: 9 levels across 2 sections, about 18 minutes end to end, roughly 4 days at five minutes a day. It moves through Grabbing and Exploring Existing Code and Publishing, Updating, and Collaborating. It starts from scratch.

9 bite-size levelsAbout 5 minutes each

Free forever · No credit card · iPhone & Android

Otto the Otter, the guide who teaches the Sharing Code on GitHub course
Sharing Code on GitHub
with Otto the Otter
9
Levels
2
Sections
5
Min/day
What you'll learn

Key ideas in Sharing Code on GitHub

  • A repository on GitHub acts as a project folder
  • It stores every past edit and version rather than just today's file state
  • Clicking 'Download ZIP' from the Code button gives immediate file access
  • ZIP downloads do not require Git software installed on the computer
  • A downloaded ZIP is a static one-off copy that won't track new changes
  • Cloning links your local folder directly to the GitHub remote repository
  • A cloned repo allows you to pull down future updates without re-downloading everything manually
  • ZIP snapshots are disconnected files that cannot receive automatic updates
  • The README file renders directly on the main page to explain what the project does and how to run it
  • The green 'Code' button provides the download and clone options
  • The Releases section houses finished milestones
  • The default repository view often contains active work in progress that might have bugs
  • The Releases tab contains specific, stable milestones that the creator marked as ready for use
  • Tags point to frozen snapshots in history meant for reliable distribution
  • Saving in an editor only updates the local file on disk, not the Git timeline
  • A commit requires an explicit action bundling chosen changes with a descriptive message
Why not just Google it

You've tried the other tabs

Wikipedia

Thirty open tabs. Four facts you actually kept.

YouTube

You watched. You nodded. By Sunday it was gone.

ChatGPT

One answer, then back to scrolling.

Online courses

Eight weeks. You meant to finish. You didn't.

Tomo gives Sharing Code on GitHub the Duolingo treatment: levels, streaks, and quick quizzes that test what you just learned. That game loop is what the tabs above never had, so it's the one you actually finish.

Try a question

Here's what playing it feels like

A real question from this course. Take your best guess.

Welcome to Your First Repository

What makes a repository special compared to a standard computer folder?

Get it right to open this lesson and 8 more in the app.

Course map

Where Sharing Code on GitHub takes you

  1. 1

    Grabbing and Exploring Existing Code

    • Finding and Downloading Repositories
  2. 2

    Publishing, Updating, and Collaborating

    • Saving Snapshots and Pushing Your Work
    • Syncing Updates and Sharing with Others

2 sections · 3 units · 9 levels. Built to play, not to enroll.

New

Tomo is in ChatGPT

Tomo is also a ChatGPT plugin: the same playable courses, built and played inside your chat.

Add Tomo to ChatGPT
How it's taught

You pick the voice

This course
The Professor

Sharing Code on GitHub is taught in the The Professor style: clear, structured, thorough. Want a different feel? In the app you can spin up the same topic in any of Tomo's teaching styles. Same facts, totally different vibe.

Keep going

More Technology on Tomo

Start free

Start Sharing Code on GitHub today.

Download Tomo, search Sharing Code on GitHub, and play your first lesson in under a minute.