Add support for modern GitFlowNext (Tower) version strings#354
Open
MavapeGZ wants to merge 1 commit into
Open
Conversation
…nce both of them are working similarlly, no more changes are required on the plugin. Readme was also updated to refer git-flow-next page
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Problem:
Since Git for Windows v2.51.1, the AVH edition of git-flow is no longer included in the installer because the original repository has been unmaintained for years. When users install the modern, actively maintained alternative—GitFlowNext (maintained by Tower)—the plugin fails to initialize and throws a Could not determine git flow version exception. This happens because the plugin strictly required the AVH string in the command output.
The Solution:
This PR updates the version validation logic to accept the modern Tower version strings while continuing to reject the unmaintained Vanilla (0.4.1) version. It also updates the documentation to help users (especially on Windows) avoid installation headaches.
Changes Made:
GitflowVersionTester.java: Modified the isSupportedVersion() method. It now converts the version string to lowercase and checks if it contains avh, tower, or next.
README.md:
Added a specific note for Windows users explaining why they might be seeing "command not found" errors on modern Git installations.
Added GitFlowNext as the recommended installation method, including a Winget command for Windows.
Clarified the version checking instructions to reflect the new supported strings.
Testing:
Verified the plugin successfully initializes without errors in the IntelliJ Sandbox environment while having GitFlowNext installed on the host system.