Please be aware that some listings have been temporarily delisted from our marketplace in order to improve the security of the platform. We apologize for any inconvenience this may caused.
For more information on this matter, please visit #1.
If you are a listing owner and would like to have your listing(s) reinstated, please open a ticket at https://gitlab.eclipse.org/eclipsefdn/it/websites/marketplace.eclipse.org/-/issues.
Thank you for your understanding and cooperation.
Reviews Sign in to post reviews
Submitted by Terry Bauer on Tue, 2020-08-11 13:59
Is there some documentation on how to use this product? I have read quite a bit on how to use Gitflow with Git, but it would be nice to have some detailed documentation on how to use the EGit derived version.
Re: Instructions ...
Submitted by Max Hohenegger on Thu, 2020-08-13 03:20
Good catch. There is a user guide, but I missed adding it to the description in this marketplace listing before. It is up there now.
This might be a bit rudimentary, and the screenshots are a bit outdated. But as always, contributions are welcome!
Re: Re: Instructions ...
Submitted by Terry Bauer on Wed, 2021-03-10 12:54
In lieu of any meaningful documentation, could you take a little time to give a simple one-line explanation as to what each menu item does?
I am making the following assumptions:
1. Start ______ initiates that particular process.
2. Finish ______ completes that process and merges into the appropriate repositories
3. Publish ______ pushes the designated item out to the GitHub repository.
However, what is the purpose of "Track Feature"?
Re: Re: Re: Instructions ...
Submitted by Max Hohenegger on Sat, 2021-03-20 08:27
@Terry, the documentation I linked to the marketplace entry, explains how to use the Gitflow EGit support.
From what it sounds like, you are new to Gitflow itself, though, and are looking for a documentation for the same. Fortunately, there is an abundance of documentation online, as well as descriptions in various text books. As with every successful project, you will also find many variants, and the variety itself may lead to more confusion. Therefore, I'd recommend you to start with the original blog post by nvie: https://nvie.com/posts/a-successful-git-branching-model/
Unfortunately, this is only a pet-project, and therefore I cannot spend a lot of time writing additional documentation. However, you are very welcome to sign-up to the Eclipse wiki, and add whatever you find missing.
Finishing a release does not merge into master
Submitted by Silvano Maffeis on Thu, 2020-02-06 08:56
When I "finish a release", the release branch is merged into develop, but it is not merged into master. Also I cannot find any tag of the release. As far as I know, according to gitflow, finishing a release should:
- Merge the release branch back into 'master'
- Tag the release with its name
- Back-merge the release into 'develop'
- (optionally) Remove the release branch
Re: Finishing a release does not merge into master
Submitted by Max Hohenegger on Mon, 2020-02-10 16:00
I cannot reproduce this issue (un)fortunately. I get both: the merge commit and the tag on the master branch.
If the operation is aborted because of a conflict you would see a respective error dialogue. Hence, I am assuming an error is thrown silently in the background. Do you see an error in the error view? Could you share exact steps to reproduce?
The plugin is out of date with GitFlow CLI.
Submitted by Vinicius Santos on Wed, 2019-07-03 14:55
1 - When a Feature Finish is performed the plugin is not performing the deletion of the remote branch related to that feature.
2 - There is no BugFix option.
I wonder if this plugin is open-source and if so how do we contribute?
Re: The plugin is out of date with GitFlow CLI.
Submitted by Max Hohenegger on Fri, 2019-07-12 03:06
> 1 - When a Feature Finish is performed the plugin is not performing the deletion of the remote branch related to that feature.
That's right. I was not even aware of that new feature in the CLI. Could you open a new bug for this with a reference to the respective CLI command? https://bugs.eclipse.org/bugs/enter_bug.cgi?product=EGit&component=Gitfl...
> 2 - There is no BugFix option.
Also correct. If you could raise another bug, that would help us!
> I wonder if this plugin is open-source and if so how do we contribute?
The plug-in is indead open source, and actually part of EGit. Both of the suggested features would be a great contribution and not too difficult to implement either. Please have a look at this part of the contributor guide: https://wiki.eclipse.org/EGit/Contributor_Guide#Automated_Developer_Setup
Bulky action to start and finish release
Submitted by Mostafa Barmshory on Thu, 2017-12-07 10:29
At the first, this is nicely integrated nice work!
My project consistes of serveral git project (PHP package manager force to create seperate git for each module). I have to release each of them at the end of the mounth. How ever it is not possilbe to select and run GitFlow action on several project at the same time.
Support for Menu
Submitted by Kevin Hermans on Tue, 2017-09-19 08:28
First of all this is the must have plugin for git in eclipse collabrate is easy the gitflow is nicely integrated nice work!
But is it also possible to add the GitFlow entry in your menu now it is somewhat to deep and directly having a gitflow entry in the menu would be a benefit for us.
Thank you for making our lives easier!
Re: Support for Menu
Submitted by Max Hohenegger on Thu, 2017-10-05 09:30
thanks for your nice Feedback! Personally I like to use the Quick Access when working with the Gitflow plug-in. Just press Ctrl+3 while a repository, a resource or an editor is selected, and start typing "start feature", and you will quickly see the command to start a new Gitflow feature. Pressing enter will execute it.
The Gitflow sub-menu is quite large, so I would prefer not to move it to the main menu (which itself is quite large already), but if you have a good idea to make the Gitflow commands available with less clicks, let me know, or better even, raise a new bug in the Bugzilla.
One option that comes to mind is adding optional toolbar actions, which could be added by the user to any perspective, using the "customize perspective" dialog. But that is just my first idea.
Support for config gitflow.*
Submitted by Andreas Bisiach on Fri, 2017-08-11 08:47
I am testing gitflow command line (1.10.2) and and your plug-in.
I have noticed that your plug-in does not respect configuration value like gitflow.feature.start.fetch=true stored in .gitconfig.
I was wondering, is it possible to configure the default behaviour of your plug-in somehow?
Re: Support for config gitflow.*
Submitted by Max Hohenegger on Wed, 2017-08-16 12:48
great to hear you want to try EGits Gitflow support. From the version you mentioned, I'm guessing you are using the gitflow-avh fork of the command line tools. Correct? Though, it looks like nvie's tools already support this configuration option .
I think it absolutely makes sense to add support for this to EGit. Could you raise a new bug in Bugzilla for this ?
Re: Re: Support for config gitflow.*
Submitted by Andreas Bisiach on Fri, 2017-08-25 09:04
Correct, 1.11.0 (AVH Edition) it's the version shipped with standard git version 2.14.1.windows.1
I have raised this bug, https://bugs.eclipse.org/bugs/show_bug.cgi?id=521414
I would actually thing that it make sense to have complete 1.11.0 (AVH Edition) support in egit gitflow since this is the standard version shipped for windows. Just my idea
Re: Re: Re: Support for config gitflow.*
Submitted by Max Hohenegger on Thu, 2018-10-18 05:26
your effort to raise the bug was not in vain! It has been fixed here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=539755
Just update the Gitflow Nightly build and have a go at it.
If you are missing other features, or find bugs, please raise the issue in Bugzilla. If you can't wait, and would like to contribute, have a look here: https://wiki.eclipse.org/EGit/Contributor_Guide#Automated_Developer_Setup
Plugin slow performance in editor
Submitted by Michael Wirth on Thu, 2015-12-17 12:02
After installing the plugin from the Marketplace (Gitflow Nightly, version 4.2.0) in STS 3.7.2 based on Eclipse 4.5.1 I experience a very slow UI response. Every key stroke requires about 5 seconds to process. Before the installation Eclipse was really running fast, but after the installation it is no use anymore.
Are these plugins not compatible? Or am I doing something wrong?
Submitted by Max Hohenegger on Mon, 2015-12-21 16:36
Thanks for your feedback! I'm not sure what could be causing this issue, so it would be great, if you could help us narrowing it down.
Did you have the Eclipse error reporting turned on? If so, any UI freezes should have been reported, and we should be able to see the details (e.g. which thread froze) soon.
Could you also try to reproduce the issue with your setup, but with this version of Gitflow instead:
In any case, feel free to open a bug here: https://bugs.eclipse.org/bugs/enter_bug.cgi?product=EGit&component=Gitflow
This will tell us if any recent commits caused this issue.
Submitted by Max Hohenegger on Sun, 2015-12-27 03:22
The issue is reportedin Bugzilla: https://bugs.eclipse.org/bugs/show_bug.cgi?id=484795
Submitted by Max Hohenegger on Mon, 2016-01-18 13:43
The issue has been resolved.