rai-story-close

To merge a git feature branch into the development branch, you need a workflow that verifies gate completion, executes a local merge preserving history, and cleans up the story branch while deferring remote push and merge requests.

You should update epic tracking immediately after merging a story branch to reflect completion, ensuring the epic scope and related tracking artifacts are updated to keep work aligned with the project roadmap.

Managing local branch cleanup without remote merge requests requires a governance workflow that handles local branch deletion and epic scope updates while explicitly deferring remote pushes and merge requests to the epic level.

Yes, merging a story branch requires a completed retrospective beforehand, as the close procedure applies gate verification and applies only when the story is fully ready for local merge and epic tracking updates.

Verifying governance gates before merging a story branch involves referencing the project manifest and known configurations to enforce gate verification, ensuring the story meets all criteria before local merge and artifact updates.

Epic level governance defers remote push and merge requests for story branches to coordinate broader epic scope updates centrally, ensuring local merges and cleanups complete before triggering remote pull requests.