Gitflow Nightly

Add this URL to your Eclipse Installation to reach this solution's update site.

2018-09 (4.9), Photon (4.8), Oxygen (4.7), Neon (4.6), Mars (4.5), Luna (4.4), 2018-12 (4.10), 2019-03 (4.11), 2019-06 (4.12), 2019-09 (4.13), 2019-12 (4.14), 2020-03 (4.15), 2020-06 (4.16), 2020-09 (4.17), 2020-12 (4.18), 2021-03 (4.19)

Learn more...
Solution Description

Nightly build of the Gitflow integration for Eclipse EGit.

User guide:

Additional Details

Eclipse Versions: 2018-09 (4.9), Photon (4.8), Oxygen (4.7), Neon (4.6), Mars (4.5), Luna (4.4), 2018-12 (4.10), 2019-03 (4.11), 2019-06 (4.12), 2019-09 (4.13), 2019-12 (4.14), 2020-03 (4.15), 2020-06 (4.16), 2020-09 (4.17), 2020-12 (4.18), 2021-03 (4.19)

Platform Support: Windows, Mac, Linux/GTK

Organization Name: The Eclipse Foundation

Development Status: Beta

Date Created: Saturday, July 11, 2015 - 05:42

License: EPL

Date Updated: Wednesday, December 14, 2022 - 09:49

Submitted by: Max Hohenegger

Subscribe to Gitflow Nightly RSS-feed

Date Ranking Installs Clickthroughs
July 2024 229/645 47 6
June 2024 230/681 74 15
May 2024 275/682 52 16
April 2024 208/687 106 11
March 2024 228/694 95 4
February 2024 236/687 76 7
January 2024 245/691 74 7
December 2023 255/671 63 7
November 2023 280/686 60 4
October 2023 220/673 107 11
September 2023 186/663 138 9
August 2023 181/673 132 5
View Data for all Listings

Unsuccessful Installs

Unsuccessful Installs in the last 7 Days: 0

Download last 500 errors (CSV)

Marketplace Drag to Install Button

By adding the following code below to your website you will be able to add an install button for Gitflow Nightly.

HTML Code:

Markdown Syntax:


Drag to your running Eclipse* workspace. *Requires Eclipse Marketplace Client

Reviews Add new review

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.


In reply to by Terry Bauer

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!

In reply to by Max Hohenegger

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"?

Thank you.


In reply to by Terry Bauer

@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:

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.

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

In reply to by Silvano Maffeis

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?

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?

In reply to by Vinicius Santos

> 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?…

> 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:…

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.



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!

In reply to by Kevin Hermans

Hi Kevin,

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.


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?



In reply to by Andreas Bisiach

Hi Andreas,

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 [1].

I think it absolutely makes sense to add support for this to EGit. Could you raise a new bug in Bugzilla for this [2]?




In reply to by Max Hohenegger

Hi Max,

Correct, 1.11.0 (AVH Edition) it's the version shipped with standard git version

I have raised this bug,

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


In reply to by Andreas Bisiach

Hi Andreas,

your effort to raise the bug was not in vain! It has been fixed here:

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:…



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?

In reply to by Michael Wirth

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:…
This will tell us if any recent commits caused this issue.