Ch. 16 · Git & CI/CD

CI Feature Flags and Lifecycle Ownership

CI Feature Flags and Lifecycle Ownership. Learn the reasoning, a practical example, common mistakes and an interview exercise.

~2 min readadvancedupdated Oct 3, 2026

Flags separate deployment from activation but add configuration states and cleanup obligations. Every flag needs an owner and retirement plan.

Before you start

You should understand commits, branches, the working tree and the staging area. Draw the commit graph before changing history. Try commands in a disposable repository with a clean working tree so you can observe exactly which references and files each operation changes.

The practical goal is to reason through this situation: Enable a new search path for a small cohort after the code is deployed. Read the walkthrough first, then try the interview exercise before opening its answer. The important part is explaining the decision and its consequences, rather than remembering a definition alone.

Step-by-step walkthrough

Step 1: Assign lifecycle ownership

Each flag needs a purpose, owner and retirement condition.

Step 2: Test supported combinations

Deployment and activation create additional configuration states.

Step 3: Remove obsolete branches

After recovery needs end, delete unused code and settings deliberately.

Worked scenario

Enable a new search path for a small cohort after the code is deployed.

A new search implementation is enabled for a small cohort after deployment. The fallback must remain compatible while rollback is needed. Once the old path is retired, leaving the flag indefinitely adds states reviewers and tests must still consider, increasing complexity without a continuing requirement.

Common mistake

Permanent unmanaged flags create combinations that are difficult to test.

Verify the behavior

Test both active paths and the flag-removal migration.

Interview exercise

Remove a completed flag safely.

Answer and reasoning

Confirm activation and rollback needs, delete obsolete branches and configuration, then validate the remaining behavior.

Continue learning

Compare the scenario with the Git and CI/CD interview questions and test your understanding with the Git and CI/CD MCQs. For terminology and implementation details, consult the reference material.

More in Git & CI/CD

read ✓Git & CI/CD · easy

Git Detached HEAD

What a detached HEAD is, when it happens, and how to keep commits made in that state.

~2 min readread →
read ✓Git & CI/CD · mid

Git Hooks and Local Automation

Automate checks with client and server hooks, share them through a framework, and enforce the same rules in CI where they cannot be bypassed.

~2 min readread →
read ✓Git & CI/CD · hard

Git LFS for Large Files

Track large binaries with Git LFS, keep pointer files in the repository, and plan for LFS storage and access.

~2 min readread →
esc