finishing-a-development-branch

To finalize a git feature branch after tests pass, you can choose between local merge, pushing to create a pull request, retaining the branch, or discarding the work. This skill validates tests and guides the chosen workflow with clear commands.

The best way to merge a development branch locally involves validating tests first, then executing a local merge into the base branch. This skill provides the exact commands and verifies that tests still pass after the merge is complete.

To create a pull request after feature development, you push the branch to the remote repository. This skill guides you through the PR creation workflow once your local tests have successfully passed.

Yes, you can retain a branch for later processing or discard the work entirely. This skill presents both options with clear execution steps, requiring explicit confirmation before discarding any development work.

Yes, this branch finalization workflow supports various Git strategies including local merges, pull request creation, and branch retention or deletion. It adapts to your team's specific workflow requirements.

You should run tests before merging a feature branch to ensure all use cases pass and the codebase remains stable. This skill enforces test validation prior to executing any merge or pull request commands.