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; } } }

How do I resolve the not a gitflow-enabled repo error when attempting to start a feature?

Shawn Fox1

I read the info at the following link, but I am still confused.

https://answers.atlassian.com/questions/157036/macos-git-flow-repo-not-enabled

OS: Windows 7 64 bit

Sourcetree: version 1.3.3.0

System Git: version 1.8.4

The following error is reported by sourcetree when I try to create a feature branch using git flow.

sh.exe C:\Users\sdfox\AppData\Local\Atlassian\SourceTree\gitflow_local\gitflow\git-flow feature start feature5

fatal: Not a gitflow-enabled repo yet. Please run "git flow init" first.

Completed with errors, see above.

So I open up a terminal and run git flow init but I get an error that "git: 'flow' is not a git command. After reading some other articles, I started searching around. I could not find any kind of program within the /usr/bin/ directory that seems related to git flow. I am now wondering if it wasn't part of the installation. Is this a git issue or a source tree issue? I'm not sure where to go from here, so I would appreciate any advice. I do have both a master and dev branch that track the remote branches. If there is any other info that I can provide, just ask. Thanks in advance!

Accepted answers

Paolo Furini

Have you initialized the repo with git-flow support using the option in the UI? You have to do it manually before start using git-flow commands in SourceTree.

SourceTree does not install git-flow globally on your system. If you want to access it directly from command line, the path should be %USERPROFILE%\AppData\Local\Atlassian\SourceTree\gitflow_local but I don't have a running win VM now, so I can't confirm that's still there in the latest version...

You can also add it to your PATH variable.

But if you plan to use Git Bash regularly, I recommend you to install git-flow in your MsysGit environment. Another (extreme) recommendation is to NOT use the nvie git-flow version that SourceTree uses, as it's somewhat buggy and is not actively maintained anymore.

I regurarly use this fork: https://github.com/petervanderdoes/gitflowIt's more powerful, stable, and actively developed. In windows u must use it at the Git Bash, but on OSX you can tell SourceTree to use your version of git-flow instead of the embedded one, and sooner or later the same option will come up in win version too (I hope).

All comments

Paolo Furini

Have you initialized the repo with git-flow support using the option in the UI? You have to do it manually before start using git-flow commands in SourceTree.

You can also add it to your PATH variable.

Shawn Fox1

"Have you initialized the repo with git-flow support using the option in the UI? You have to do it manually before start using git-flow commands in SourceTree."

Within SourceTree, if I select < Repository, Git Flow >, then the Initialize Repository option is already grayed out. In my mind, that means that it has already been done. Yet the GUI still tells me that I need to do it when I try to begin a new feature.

Shawn Fox1

I setup an alias to the path that you mentioned. git-flow is in fact located there. Thank you for pointing that out. I setup an alias to quickly run it. The result was a different error "flags:FATAL unable to determine getopt version"

Paolo Furini

Yes, the git-flow command in MsysGit requires some libs to be in place to work. See https://github.com/nvie/gitflow/wiki/Windows#wiki-msysgit

If you really want to use git-flow at the git bash, I strongly recommend you to install a fresh copy using the instructions in the link above. If you plan to use git-flow BOTH in the command line and in SourceTree, then use the nvie code in the above link. If u want to use ONLY in the command line, install the fork I pointed out in my original answer.. it works (far) better, but you should pay attention to NEVER use the GUI anymore to issue git-flow commands.

Regarding your repo, close SourceTree, then open the "config" file under the .git directory, and delete the sections that start with [gitflow ...] (for example gitflow "branch" and gitflow "prefix") and all the settings under them. I don't know if SourceTree places a custom flag in its "sourcetreeconfig" file, try to open it and if you find something like "gitflowenabled=1" then you should delete it...

Then start SourceTree and see if the option to enable git flow in your repo is enabled again.

Hope this helps..

johnbarnaby

This explanation from Kieran Senior [Atlassian] helped me to better understand this and other similar problems using SourceTree GitFlow at: https://answers.atlassian.com/questions/146292/git-flow-post-initialization-issue-recovery.

jpfl

Although this is an old post, just wanted to add to this since I've gotten stuck on this same error. Was able to resolve by doing the following:

Open the .git\config file
Remove all the [gitflow * entries and save the file
Close and re-open SourceTree
In the main menu, go to Repository > Git Flow > Initialise Repository (should be enabled now)

Once I did this, was able use the GitFlow functionality again (start new branches, finish releases, etc). Hopefully this will work for any others who encounter this problem.

phouvadolh mano1

Thx! It resolves my problem. imo, TortoiseGit may interfer with .git/config file when TortoiseGit and SourceTree are both installed.

Shaun Burch

Thank you jpfl, this also resolved my issue!

Tomáš Beňo

This fixed the issue. I believe the problem was that I removed my "master" branch because I was never even using it and that broke git flow.

analerma

For me (and as someone mentioned above), the problem was that I had deleted the master branch from my local. Checking out the master branch again fixed my problem, and this solution was simpler than jpfl's.

arich

I had the same issue this morning as well. After checking out both the master and develop branches locally the error message went away.

Welcome!

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

Quick Links

Find more posts tagged with

sourcetree

git

git-flow