I built a game that only grows when you push real GitHub commits. Roast it?

# github# productivity# 100daysofcode# buildinpublic
I built a game that only grows when you push real GitHub commits. Roast it?Vishal Pandey

I'm the solo dev behind this, so take my enthusiasm with salt. My problem: I start side projects and...

I'm the solo dev behind this, so take my enthusiasm with salt.

My problem: I start side projects and quietly drop them around week three. So I built Vigilante, a free game where you connect one repo, and your settlement only grows when you push verified work. No push, no daily supply crate.

How it works, briefly:

  • You connect a single GitHub repo. It never clones the repo or reads your source, private diffs, or credentials. It only sees push signals.
  • Verified pushes earn daily supplies that build six buildings (Lantern House, Salvage Yard, and so on).
  • Streaks give bonuses, and there's one "mend a missed day" item a month so a bad day doesn't wreck everything.
  • There's a story campaign, plus a daily share card if you want to show your progress.

It's free to start. There's also a free GitHub check-up that audits your repo's recent activity with no signup, in case you only want that.

What I'd like to know:

  • Does "game progress tied to real commits" feel motivating, or gimmicky?
  • What would make you stop using it after day 3?
  • Is "it doesn't read your code" enough to make you comfortable connecting a repo?

Link: https://vigilante.ocix.in

Happy to answer anything, including "why does this exist."