What Is a Pull Request? How Website Code Changes Get Reviewed

The six points in the video

This is a silent video. The headings, explanations and labels below reproduce the information on screen.

1. 1

   Step 1: Describe the proposed update

   0:18

   Explain what changed and the problem it addresses.

   On-screen labels: Change summary; Reason for change; Related task.

2. 2

   Step 2: Inspect the actual differences

   0:30

   The file comparison shows the proposed code changes.

   On-screen labels: Changed files; Added content; Removed content.

3. 3

   Step 3: Review available checks

   0:42

   Build and test results can provide evidence about the update.

   On-screen labels: Build result; Relevant tests; Known limitations.

4. 4

   Step 4: Use the discussion

   0:54

   Review comments can identify questions and improvements.

   On-screen labels: Reviewer questions; Author response; Resolved feedback.

5. 5

   Step 5: Know the draft status

   1:06

   A draft pull request signals that work is still in progress.

   On-screen labels: Work in progress; Further changes; Ready for review.

6. 6

   Step 6: Keep release status clear

   1:18

   A merged change may still need a separate production deployment.

   On-screen labels: Merge status; Deployment status; Live-site verification.

Common questions

Go further