What is a pull request checklist you actually use?
PICTURE THIS: GIT FLOW
Simple meaning
Tests green, no secrets, clear description, and screenshots for UI.
WHY — Git instead of guessing?
Why interviewers care about Git:
who only read docs from people who shipped.
and tied to Full Stack work.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1Tests green, no secrets,
clear description, and screenshots for UI.
- 2I ask for one
reviewer who knows the area.
- 3Tiny PRs merge faster
than mega dumps.
- 4Give an example
One tiny concrete case you can say aloud.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
Tests green, no secrets, clear description, and screenshots for UI. I ask for one reviewer who knows the area.