Status is always shown as No gitflow
See original GitHub issue-
I’m submitting a …
- bug report
- feature request
- puppy => You’re not submitting a puppy. I already have one and he’s adorable
-
What is the current behavior? On repositories where gitflow is setup, the status bar shows as No gitflow. I have tried to re-init the git flow by doing a
git flow init -f
but the result is still the same. -
Is this a bug? Sorry about that. If so give me explicit details how to reproduce:
- Open PhpStorm
- Install version 0.7.0 (modify the metadata info to get it installed in build 193)
- Notice in the bottom corner that the status is shown as No gitflow
-
What is the expected behavior? That there is the option to perform git flow operations.
-
What is the motivation / use case for changing the behavior? It does not work as expected at the moment.
-
Please tell me about your environment:
-
Gitflow4idea version: 0.7.0
-
Gitflow version: 0.4.1
-
IntelliJ Help -> about > click copy icon and paste here. Should look like this:
-
PhpStorm 2019.3 EAP
Build #PS-193.3519.40, built on September 23, 2019
PhpStorm EAP User
Expiration date: October 23, 2019
Runtime version: 11.0.4+10-b480.2 x86_64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
macOS 10.14.6
GC: G1 Young Generation, G1 Old Generation
Memory: 2048M
Cores: 8
Registry: run.processes.with.pty=TRUE, debugger.watches.in.variables=false
Non-Bundled Plugins: BashSupport, Gitflow, String Manipulation, com.kalessil.phpStorm.phpInspectionsEA, izhangzhihao.rainbow.brackets, net.seesharpsoft.intellij.plugins.csv
- Other information (e.g. detailed explanation, stacktrace, related issues, suggestions how to fix, links for me to have context words of praises, pictures of puppies (again with the puppy??) ) Running git flow commands from the command line works.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:6
- Comments:11 (2 by maintainers)
Top Results From Across the Web
The problem with Git flow - GitLab
Learn why Git flow complicates the lifecycle and discover an alternative to streamline development.
Read more >Git Flow CLI Incompatible With GitHub Protected Branches
I am not precisely sure what github isn't happy about, whether it's because the feature branch is deleted without being merged via their...
Read more >Don't Fear the Repo: Enhanced Git Flow Explained - Toptal
The "Git flow" model is both popular and controversial. To see Git flow explained, the complexity of everyday operations becomes clear.
Read more >Git Flow Workflow · SciCat Documentation
master - always ready to deploy (manual/time delayed integrations from the ... In essence, without this flag, there will not be a visible...
Read more >Please stop recommending Git Flow! - George Stocker
No thank you. While I hesitate to say “Worrying about merge conflicts” is a valid reason not to pursue a branching strategy like...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@gn-jgeerds Thank you for the tip.
So I did the following:
git-flow
git-flow-avh
git flow init -f
The only thing I do see (or rather not) is the gitflow icon:
Notice the empty space before the lock, I have to click there to see this:
Any tips for that? 😉
Edit: This only seems to happen on projects with multiple git repos (submodules)
@gn-jgeerds Thank you, too. Switching to git-flow-avh solved the problem for me, too 😊
@OpherV: Hope you had a nice vacation! Perhaps your plugin could check git flow version and show some notice on 0.4.1…