Skip to main content
Apply for a Cheap Website
Website explainer · 1:47

Git Branches Explained: A Separate Line of Website Development

How can a developer work on an update separately? A branch provides a separate line of development in a repository.

Jersey Web video: Work on a separate branch

1:47 · No narration: the video shows each step as text on screen, and every step is written out below, with buttons that jump the video to it.

Download the on-screen text track (VTT)

The six points in the video

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

  1. Step 1: A branch starts from existing work

    It begins from a point in the project history.

    On-screen labels: Existing project; Starting point; New line of work.

  2. Step 2: Changes can be developed there

    A feature or fix can progress without updating the main branch.

    On-screen labels: Feature work; Bug fix; Separate development.

  3. Step 3: A branch name gives context

    A descriptive name helps the team identify its purpose.

    On-screen labels: Clear name; Specific purpose; Related task.

  4. Step 4: Review compares the changes

    A pull request can compare proposed work with another branch.

    On-screen labels: Proposed changes; Target branch; Review discussion.

  5. Step 5: Merging combines the work

    The accepted changes become part of the target line of development.

    On-screen labels: Reviewed update; Merge decision; Combined project.

  6. Step 6: Live publishing depends on setup

    Some branches create previews; production rules vary by project.

    On-screen labels: Preview rules; Production rules; Actual deployment.

A practical check for your business

Agree how work moves from a development branch into the released site. A separate branch supports the workflow, but a change still needs an appropriate review and deployment check.

Sources and further detail

Common questions

How can a developer work on an update separately?

A branch provides a separate line of development in a repository. Check the branch, review and deployment status separately.

Go further

Guide Read the practical guide More context for planning and maintaining your business website. 5 min read → Jargon Buster Branch explained Read the related Jargon Buster explanation. Read the explanation →

Check the branch, review and deployment status separately.

Tell Jersey Web what your website needs to do and which part you want help with.

Talk to Jersey Web →

More video tips

All 205 videos →
Length 1:47 Website development

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

Pull requests, explained.
Length 1:47 Website development

Website Deployment Explained: From Project Files to a Running Site

Publishing website code changes.
Length 1:47 Website development

Website Rollbacks Explained: Returning to an Earlier Deployed Version

Understand the rollback plan.