WEBVTT

00:00:00.000 --> 00:00:06.000
How can a developer work on an update separately?

00:00:06.000 --> 00:00:13.000
A branch provides a separate line of development in a repository.

00:00:13.000 --> 00:00:18.000
Follow the proposed change.
6 branch basics.

00:00:18.000 --> 00:00:30.000
A branch starts from existing work
It begins from a point in the project history.
Existing project · Starting point · New line of work

00:00:30.000 --> 00:00:42.000
Changes can be developed there
A feature or fix can progress without updating the main branch.
Feature work · Bug fix · Separate development

00:00:42.000 --> 00:00:54.000
A branch name gives context
A descriptive name helps the team identify its purpose.
Clear name · Specific purpose · Related task

00:00:54.000 --> 00:01:06.000
Review compares the changes
A pull request can compare proposed work with another branch.
Proposed changes · Target branch · Review discussion

00:01:06.000 --> 00:01:18.000
Merging combines the work
The accepted changes become part of the target line of development.
Reviewed update · Merge decision · Combined project

00:01:18.000 --> 00:01:30.000
Live publishing depends on setup
Some branches create previews; production rules vary by project.
Preview rules · Production rules · Actual deployment

00:01:30.000 --> 00:01:39.000
Your checklist
A branch starts from existing work · Changes can be developed there · A branch name gives context · Review compares the changes · Merging combines the work · Live publishing depends on setup

00:01:39.000 --> 00:01:47.000
Check the branch, review and deployment status separately.
jerseyweb.je