Git and GitHub for Product Managers
The Four States Work Can Be In
When you want to know where something is, there are only four answers, and each has a different place to look.
State | Where to Look | What You'll See |
|---|---|---|
Not started | Issues tab, or your tracker | An issue with no linked PR |
In progress | Branches view | A branch with recent commits, no PR yet |
Proposed | Pull requests tab | An open PR, possibly with review comments |
Landed | Commits on main, or Releases | A merged PR; possibly in a release |
COPY THIS PROMPT — Understanding Your Team's Branch Workflow
Help me understand how my engineering team's branching and release
process works, so I can interpret what I see in GitHub.
WHAT I'VE OBSERVED
Branch names I see: [paste a few real branch names]
Our main branch is called: [name]
Other long-running branches: [any, e.g. develop, staging]
How often we release: [continuously / weekly / fortnightly / ad hoc]
Do we use feature flags: [yes / no / don't know]
Please:
1. Which of the common branching shapes does this look like?
2. When a PR is merged, what's the likely path from there to a
customer seeing it? Walk through the steps.
3. Given this setup, what does 'done' most likely mean when my
engineers say it?
4. Write five specific questions I should ask to confirm my
understanding, phrased as curiosity rather than scrutiny.
5. What would I look at to tell, myself, whether a specific
feature is live right now?