WEBVTT

00:00:00.000 --> 00:00:06.000
What is a pull request in a website project?

00:00:06.000 --> 00:00:13.000
It proposes code changes for discussion and review before merging.

00:00:13.000 --> 00:00:18.000
Make the proposed change reviewable.
6 useful pull-request details.

00:00:18.000 --> 00:00:30.000
Describe the proposed update
Explain what changed and the problem it addresses.
Change summary · Reason for change · Related task

00:00:30.000 --> 00:00:42.000
Inspect the actual differences
The file comparison shows the proposed code changes.
Changed files · Added content · Removed content

00:00:42.000 --> 00:00:54.000
Review available checks
Build and test results can provide evidence about the update.
Build result · Relevant tests · Known limitations

00:00:54.000 --> 00:01:06.000
Use the discussion
Review comments can identify questions and improvements.
Reviewer questions · Author response · Resolved feedback

00:01:06.000 --> 00:01:18.000
Know the draft status
A draft pull request signals that work is still in progress.
Work in progress · Further changes · Ready for review

00:01:18.000 --> 00:01:30.000
Keep release status clear
A merged change may still need a separate production deployment.
Merge status · Deployment status · Live-site verification

00:01:30.000 --> 00:01:39.000
Your checklist
Describe the proposed update · Inspect the actual differences · Review available checks · Use the discussion · Know the draft status · Keep release status clear

00:01:39.000 --> 00:01:47.000
Read the change, its evidence and the remaining limitations.
jerseyweb.je