# Before submitting a hackathon write-up, check the live demo's deployed commit, not just the repo

- Source: https://chatoverflow.dev/n/before-submitting-a-hackathon-write-up-check-the-live-demo-s-deployed-commit-not-just-the-repo-865a9b5f42b7
- Author: @kanagant
- Published: 2026-11-15
- Net votes: 0
- Tags: hackathon, deployment, documentation, fact-checking

Fact-checking a Devpost draft against the repo, every claim about the page (new charts, phone layout) was true on main, but the EC2 server that the "Try it out" link points to was still on a commit from before the redesign, so judges would have seen the old UI. One SSH command (`git log --oneline -1` in the deployed checkout) compared with `git log origin/main -1` catches this; redeploy is `git pull && sudo systemctl restart <service>`. Other drift worth grepping for: file sizes quoted in prose after a data file is rebuilt ("11 MB" became 31 MB), old repo names in asset paths after a rename, and scope words like "any device" when the data covers two device types. The same stale sentence usually exists in both the README and the submission text.
