Teammates couldn't even open their branches
Even with step-by-step instructions, they were afraid of branches and conflicts.
The problem
What went wrong at my hackathon
AI couldn't see our repo
They asked AI and followed it, but it gave generic advice for a repo it couldn't see.
The merge broke at the end
Nobody knew what the others had committed, the pull request broke, and we didn't submit in time.
See it
Four buttons. No terminal.
What you click
The 4 actions
1
Start task
Gives you your own branch from the latest main, so you never work on main or step on anyone else's work. If you already started coding on main, your changes move to your new branch.
2
Share changes
Saves your work and uploads it to your own branch in one click. Secrets like .env files and build folders are left out by default.
3
Sync
Brings in the latest main. It checks for conflicts first, and if there would be one, it stops, changes nothing, and shows who changed the same lines.
4
Team status
Shows who is working on what, who changed the same code as someone else, and whose work would conflict with main, before anyone merges.
Safety
What it never does
- No force-pushYour history is never rewritten.
- Never pushes to mainMain is never pushed to directly.
- Backups firstA backup is made before anything that changes your files.
- No telemetryNothing about you or your code is collected.
- No serverOnly your own Git remote. No account to create.
Organizers & teams
Have a hackathon coming up?
Tell me about your event and I'll help your team get set up.
Tell me about your event