finishing-a-development-branch

To complete a development branch after tests pass, you can use this Skill to verify tests and then choose to merge locally, create a pull request, keep the branch, or discard it. It requires git and GitHub.

The best way to manage feature branch cleanup is to use a structured workflow that verifies tests first, then presents options like local merge, pull request creation, or branch deletion to ensure code quality and consistency.

This branch management workflow requires both git and GitHub for branching and merging. You need GitHub specifically to execute the pull request creation option when finishing your feature branch.

Test verification works by ensuring all tests are passed before presenting any merge, pull request, or cleanup options. This guarantees code quality and workflow consistency before a feature branch is completed.

Your options for finishing feature branch work include performing a local merge to a base branch, pushing to create a pull request, keeping the branch as-is, or discarding the branch entirely.

Yes, you can discard a development branch instead of merging it. This Skill presents branch cleanup options after test verification, allowing you to safely discard the branch if the feature is no longer needed.