branches.md

New term: branch

• A sequence of commits (changes) is referred to as branch.
• A new branch can be created by branching off from a commit on another branch.
• A branch can be understood as a named version of your repository.

Development scheme

Generally, in a repository, there are guidelines for contributing.

A common development scheme is dual with a:

• development version on develop
  • things are still being changed and mistakes are being fixed
• stable version on master
  • actively used version in production environment

In the practice repository, the development branch is called develop!

Use this dual development scheme for your own repositories!

Create your own version

Assume that you want to work on a new content.

Best practice is to create a new branch!

Using branches ensures:

• your changes are made separately from other (unrelated) changes
• your version will not be affected by other contributors
• all related changes are aggregated in one place
• work can continue if the development of one feature gets stuck

Are you working on more features in parallel?

Create a new branch! for each of them!

Quick recap

What is the difference between a fork and a branch?

How to switch between branches?

Why is it best practice to branch off from develop?