To address challenges with large pull requests (PRs) that hampered effective reviews and rushed merges, teams implemented epic branches. These branches allow developers to group related work while ensuring that unfinished code does not impact the mainline. Each large project is tracked under an epic branch, where individual components are merged as small, focused PRs. Importantly, the epic branch retains an informative history, allowing for concurrent development on dependent features, ultimately improving collaboration without the chaos of rebasing.
We now create epic branches for every large project, using the naming convention epic/feature-name - for example: epic/new-checkout-flow.
One of the best parts? Epics can be based on other epics. This lets us start work on dependent features without waiting for the base feature to fully ship.
Collection
[
|
...
]