@studnicky/git-flow@0.3.0
Minor Changes
-
#23
f6423e2Thanks @Studnicky! -feature/release/hotfixnow adapt to the target repository's actual merge settings instead of hardcoding a strategy.MergeMethodResolverresolves a real, available method from an ordered preference list (GithubPrimitives.repositoryMergeCapabilitiesreadsallow_merge_commit/allow_rebase_merge/allow_squash_mergefrom the repo). Feature branches intodevelopstill prefer squash, falling back to merge or rebase if squash happens to be disabled. Release/hotfix promotions intomainnever squash — merge or rebase only — since squashing collapses the promoted branch's history that the subsequent back-merge intodevelopdepends on; if a repo only allows squash, this now fails loudly with a clear error instead of silently squashing and corrupting the next back-merge.MergeMethodEntitygains'rebase'as a third valid value.feature/release/hotfixalso now install a default PR template into the target repository before opening a PR, if — and only if — that repository doesn't already have one at any of GitHub's recognized template locations. Never overrides an existing template. The bundled default uses GitHub's alert callouts (> [!CAUTION]/[!IMPORTANT]/[!TIP]/[!NOTE]) to color-code Type of Change and Risk by actual severity, a collapsible<details>block for an optional change-flow diagram, and an adversarial-self-review gate ahead of the checklist instead of a habit-checked box list.