finishing-a-development-branch

To finish a git development branch after tests pass, the skill verifies test results, determines the base branch, and presents four structured options: merge locally, push and create a pull request, keep the branch, or discard it.

Automating a git branch merge decision involves evaluating the current feature branch state and presenting deterministic integration choices. This skill recommends a repeatable workflow to conclude development by executing the chosen git action automatically.

Yes, you can choose between a local merge and a pull request when finishing a feature branch. The skill lists both options alongside keeping or discarding the branch, then executes your chosen action via git commands.

To discard or keep a development branch instead of merging, you select the respective option from the four structured choices presented by the workflow. The skill then executes the chosen git command to retain or remove the branch.

Yes, this workflow requires passing tests before integrating a feature branch. It applies to feature branches ready for merge and verifies test results before presenting the four structured options to finalize the development work.

Automating development branch finishing is limited to scenarios where tests pass and a defined team workflow is needed. It focuses on executing four specific git actions and does not handle complex merge conflict resolution.