A branch without an owner becomes archaeology.
Long-lived branches need a purpose, a steward, and a clear end condition.
Interpretation
Branches age like food, not wine. As the target moves, conflicts grow and assumptions decay. A named owner keeps the work rebased, explains whether it is still needed, and closes it when the experiment ends. Ownership prevents abandoned intent from becoming repository sediment.
Practice
- Name an owner in the pull request.
- Prefer short-lived branches and incremental integration.
- Review and delete stale branches regularly.
Anti-pattern
Keeping a six-month branch “just in case” after its author leaves.

