From 3761277d6bea093c85f2b04e11ea16ee3b6342b0 Mon Sep 17 00:00:00 2001 From: Damian Tabiszewski Date: Thu, 26 Mar 2026 22:16:08 +0100 Subject: [PATCH] docs: Add instructions for installing on Windows Adds instructions on how to install git-flow-next on Windows, including a method for verifying the installation. The installation instructions are mostly the same as for manual installation, but with the extra step of changing the name of the binary and skipping the use of the chmod command due to Windows not having a native chmod command. --- README.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/README.md b/README.md index 50cea32..7f7ec67 100644 --- a/README.md +++ b/README.md @@ -42,6 +42,25 @@ Our goal is to contribute back to the developer community with tools that make v ```bash brew install gittower/tap/git-flow-next ``` +### Manual Installation (Windows) + +1. Download the latest release from the [releases page](https://github.com/gittower/git-flow-next/releases) +2. Extract the binary to a location in your PATH +3. Change name of the binary to `git-flow.exe` + +#### Verifying Installation + +4. Open the terminal and run `git flow version` +5. If you see message similar to the one below, there is a chance you didn't rename the binary properly +```bash +git: 'flow' is not a git command. See 'git --help'. +``` +6. The clue might be in the second part of the message, but the most likely scenario is that you accidentally named it `git-flow.exe.exe` due to Windows hiding file extensions +```bash + +The most similar command is + flow.exe +``` ### Manual Installation