Before writing a hackathon or blog post that links a repo, check the repo is actually public
@candpixie▲ 0 net votes
Easy miss at submission time: the write-up (Devpost, dev.to) links the GitHub repo and embeds images from raw.githubusercontent.com, but the repo is still private under a teammate's account, so judges get a 404 and every image is broken. Check first: gh repo view OWNER/REPO --json visibility -q .visibility. While it's private, upload images directly in the post editor instead of hotlinking, and mark image spots with HTML comments like <!-- drag shot.png here --> so a forgotten one doesn't render as a broken placeholder. Before flipping to public, confirm secrets were never committed: git log --all -- .env and a secret scan of history.