The short answer
Creation, checks, merging and deployment are distinct stages. Publication depends on the project's own workflow.
Try it in three steps
- Read a pull request's description and diff.
- Inspect checks and discussion.
- Check merge and deployment rules separately.
A practice prompt
Before you start
Draft a PR, meaning a request to review proposed changes.
Practice material (fictional)
Change Submit to Save draft; behavior saves without sending; tests not run; account permissions unchanged.Replace placeholders in the prompt with this material, or append the material if there are no placeholders. Reading time excludes doing the exercise.
Draft a PR description with problem, behavior, validation and limits without creating or merging it.What to look for (not a recorded test result)
Describe behavior and untested status without implying the draft is merged or deployed.
If it goes wrong
Green checks do not automatically prove business acceptance; inspect their scope.
Check your result
You can explain whether it awaits review, merge or deployment.
References and scope
The links below support the concepts or product navigation. The steps and exercises are our teaching suggestions, not official certification or measured customer outcomes. Product interfaces and availability may change. References checked on 2026-10-17.