nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

GitFlow "broken" on v 0.9.3.0?

Johan Leino

Hey,

after upgrading to v 0.9.3.0 I get this whenever starting a new feature (test in this example):

git flow feature start test

git: 'flow' is not a git command. See 'git --help'.

Did you mean one of these?

reflog

show

The repo has been initialized before and worked with previous version (click-once btw)

Ideas?

Update

I get this on a fresh repo when trying to init GitFlow:

git flow init -d

git: 'flow' is not a git command. See 'git --help'.

Did you mean one of these?

reflog

show

Accepted answers

stevestreeting

We did change how git-flow was located in 0.9.3, in order to fix a couple of problems with the 'rebase' option of finishing features and releases, however I've tested this on a couple of machines without any issues, using both the system Git install and embedded Git install. Both init and other functions appear to work fine.

The change was that instead of directly calling the git-flow script, we add its location to the PATH, which allows it to call itself. The location is %USERPROFILE%\AppData\Local\Atlassian\SourceTree\gitflow_local, can you check if that exists for you? If it does, can you confirm the full path?

All comments

stevestreeting

Johan Leino

No, that location is not in my PATH.
However, I added this manually %USERPROFILE%\AppData\Local\Atlassian\SourceTree\gitflow_local\gitflow and that seemed to do the trick.

stevestreeting

Sorry, I actually meant that SourceTree adds this to the PATH of the git process when it calls it - it doesn't alter your global PATH. It's interesting that adding this to your PATH worked though, that makes me wonder if your PATH is already quite long or something like that which is stopping the SourceTree addition to the git processes PATH from working?

Johan Leino

Ah, ok got it. No my Path ain't that long. It's not a permission issue?? Also, note that the location I added wasn't the same as you posted but that might have been a typo on your side perhaps!?

Johannes Kilian_pi36cl

Updating to SourceTree 0.9.4 resolves my issues described above

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

sourcetree

windows

git-flow