Process··8 min read
From Issue to Deploy: A Real GitHub Workflow
How I keep the Issue → Branch → PR → Review → CI → Deploy chain simple and repeatable on small teams.
Most projects break not while writing code, but when trying to ship changes safely. For me, the backbone of the flow is GitHub Issues.
Every piece of work starts with an issue: problem statement, acceptance criteria, labels. The branch name ties to the issue number. No merge without a PR; no review counted complete until CI is green.
The deploy step should be as boring as possible: staging automatic, production manual approval or tag. No surprise deploys.
This discipline lowered crash rates and the “which commit is live?” uncertainty on products like Picadoo and JuriScore.