Why Gitflow workflow? - Purpose & Use Cases

The Big Idea

What if your team could work together without ever overwriting each other's work by accident?

The Scenario

Imagine you and your friends are writing a big story together, but everyone is editing the same paper at once without any plan.

It quickly becomes confusing who wrote what, and fixing mistakes means erasing others' work.

The Problem

Working without a clear plan causes lost changes, accidental overwrites, and lots of time spent fixing errors.

It's like trying to build a puzzle with pieces from different boxes mixed up.

The Solution

Gitflow workflow gives you a clear map for working together.

It separates your work into branches like 'main' for finished parts, 'develop' for ongoing work, and special branches for new features or fixes.

This way, everyone knows where to add their changes safely without breaking the story.

Before vs After

✗ Before

git commit -am "fix bug"

✓ After

git checkout -b feature/new-idea
git add .
git commit -m "add new idea"
git checkout develop
git merge feature/new-idea

What It Enables

It enables smooth teamwork where many people can build, test, and improve code without stepping on each other's toes.

Real Life Example

A software team uses Gitflow to add new features, fix bugs, and prepare releases in an organized way, so the app stays stable and improves steadily.

Key Takeaways

Manual collaboration causes confusion and errors.

Gitflow organizes work into clear branches for safety and clarity.

This workflow helps teams deliver better software faster and with less stress.

Practice

1. What is the main purpose of the develop branch in the Gitflow workflow?

easy

A. It serves as the integration branch for features before release.

B. It contains the production-ready code only.

C. It is used to fix urgent bugs directly in production.

D. It stores experimental code that is not stable.

Solution

1. Step 1: Understand the role of the develop branch

   The develop branch is where all completed features are merged and tested together before release.

2. Step 2: Compare with other branches

   The master branch holds production-ready code, hotfix branches fix urgent bugs, and experimental code is not part of Gitflow standard branches.

3. Final Answer:

   It serves as the integration branch for features before release. -> Option A

4. Quick Check:

   Develop = integration branch [OK]

Hint: Develop branch integrates features before release [OK]

Common Mistakes:

• Confusing develop with master branch
• Thinking develop is for hotfixes
• Assuming develop holds only stable code

2. Which command correctly starts a new feature branch named login using Gitflow?

easy

A. git flow start feature login

B. git flow feature start login

C. git start feature login

D. git feature start login

Solution

1. Step 1: Recall Gitflow feature start syntax

   The correct syntax to start a feature branch is git flow feature start <name>.

2. Step 2: Check each option

   Only git flow feature start login matches the correct syntax exactly. Others have incorrect order or missing 'flow'.

3. Final Answer:

   git flow feature start login -> Option B

4. Quick Check:

   Feature start = git flow feature start [OK]

Hint: Use 'git flow feature start <name>' to start features [OK]

Common Mistakes:

• Omitting 'flow' in the command
• Swapping command word order
• Using 'git start' instead of 'git flow feature start'

3. Given the commands below, what is the final branch after finishing a release?

git flow release start 1.0.0
git flow release finish 1.0.0

medium

A. The branch is switched to master.

B. The branch is switched to develop.

C. The branch remains on release/1.0.0.

D. The branch is switched to feature/1.0.0.

Solution

1. Step 1: Understand what 'git flow release finish' does

   This command merges the release branch into both master and develop, tags the release, and deletes the release branch.

2. Step 2: Identify the branch after finishing release

   After finishing, Gitflow switches to master branch by default.

3. Final Answer:

   The branch is switched to master. -> Option A

4. Quick Check:

   Release finish switches to master [OK]

Hint: Release finish merges and switches to master [OK]

Common Mistakes:

• Assuming branch stays on release
• Thinking it switches to develop
• Confusing feature branches with release

4. You ran git flow feature finish login but your changes are not in develop. What is the likely problem?

medium

A. You forgot to push the develop branch after finishing the feature.

B. You did not commit changes before finishing the feature.

C. You started the feature branch from master instead of develop.

D. You finished the feature on the master branch.

Solution

1. Step 1: Recall feature branch base in Gitflow

   Feature branches should start from develop to ensure changes merge back there.

2. Step 2: Analyze why changes are missing in develop

   If the feature branch was started from master, finishing it merges changes into master, not develop, causing missing updates in develop.

3. Final Answer:

   You started the feature branch from master instead of develop. -> Option C

4. Quick Check:

   Feature base must be develop [OK]

Hint: Feature branches must start from develop [OK]

Common Mistakes:

• Assuming finishing auto-pushes changes
• Not committing before finishing
• Confusing master and develop as base

5. Your team wants to prepare a hotfix for a critical bug in production while a release is in progress. According to Gitflow, which sequence of commands correctly handles this situation?

hard

A. git flow hotfix start fix-bug; git flow release finish; git flow hotfix finish fix-bug

B. git flow release finish; git flow hotfix start fix-bug; git flow hotfix finish fix-bug

C. git flow feature start fix-bug; git flow feature finish fix-bug

D. git flow hotfix start fix-bug; git flow hotfix finish fix-bug

Solution

1. Step 1: Understand hotfix purpose in Gitflow

   Hotfix branches are created from master to quickly fix production bugs, independent of ongoing releases.

2. Step 2: Check command sequence for hotfix

   Starting and finishing a hotfix with git flow hotfix start and git flow hotfix finish is the correct way, regardless of release status.

3. Step 3: Evaluate options

   git flow hotfix start fix-bug; git flow hotfix finish fix-bug correctly starts and finishes the hotfix. git flow release finish; git flow hotfix start fix-bug; git flow hotfix finish fix-bug delays hotfix until release finishes, which is not required. git flow feature start fix-bug; git flow feature finish fix-bug uses feature instead of hotfix. git flow hotfix start fix-bug; git flow release finish; git flow hotfix finish fix-bug incorrectly mixes release finish before hotfix finish.

4. Final Answer:

   git flow hotfix start fix-bug; git flow hotfix finish fix-bug -> Option D

5. Quick Check:

   Hotfix runs independently during release [OK]

Hint: Hotfix branches start and finish independently from release [OK]

Common Mistakes:

• Waiting for release to finish before hotfix
• Using feature branch for hotfix
• Finishing release before hotfix finish