Code & Collaboration
$definegithub--plain-english
TLDRWhere the code lives and gets shared.
GitHub is the shared studio wall.
Your laptop has the sketchbook (Git). The wall is where you hang the latest pages so the rest of the crew can see them — a teammate, a judge who wants the repo, an agent cloning the project. The folder on that wall is a repo. Sending pages up is a push. Taking pages down is a pull. Copying the whole wall to a new laptop is a clone.
People say "GitHub" the way they say "the office." GitLab and Forgejo are other buildings. Same job: a place the book lives when your lid is closed.
The wall is also the bulletin board
Issues. Pull requests. Actions. The green squares. Open source projects hang here so anyone can read them, fork them, or install them as a dependency. Half the builder stack is a list of things that already live on this wall.
Close the lid and leave the venue. The wall still has the pages. That is the unglamorous reason you push before you sleep. npx create-hackhaton-space-stack@latest gives you a local repo. It is not on the wall until you hang it.
Agents via MCP or the plugin already know this building. "Clone that," "open a PR," "push" — they are walking pages between your bench and the wall.
Public means the sidewalk can read it
Most hackathon repos are public. Bots stroll by looking for secrets. A key in the repo is a credit card taped to the glass. Keep keys in .env. Never in a commit you push.
What this unlocks
A project that exists when your laptop does not. A door teammates and agents already know how to open.
Hang the pages. Then go sleep.