Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 473647 - When on master branch, gitflow options are disabled.
Summary: When on master branch, gitflow options are disabled.
Status: RESOLVED FIXED
Alias: None
Product: EGit
Classification: Technology
Component: Gitflow (show other bugs)
Version: 4.0   Edit
Hardware: All All
: P3 normal with 1 vote (vote)
Target Milestone: 4.1   Edit
Assignee: Max Hohenegger CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-27 08:13 EDT by Peter Boughton CLA
Modified: 2015-09-27 16:56 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Boughton CLA 2015-07-27 08:13:10 EDT
I was going to see whether hotfixes are correctly handled, but upon switching to the master branch the option is not even available.

Given that hotfixes are branched from master, this option should be available here!

Indeed, all three "start x" options should always be available, and simply switch to the correct branch beforehand (i.e. develop for feature/release, master for hotfix).
Comment 1 Max Hohenegger CLA 2015-07-27 09:49:06 EDT
> I was going to see whether hotfixes are correctly handled

Did you try it on develop as well?
Comment 2 Peter Boughton CLA 2015-07-27 10:10:43 EDT
When on develop, start hotfix branches from master (correct).
Finish hotfix is merging into develop (correct) and tagging develop (incorrect).
Finish hotfix does not appear to merge to trunk (incorrect).

So the solution for this issue is to make (at least) start hotfix option available on trunk - though ideally all "start x" options would be available whichever branch is active.

The incorrect merging/tagging behaviour is a separate issue and can be covered by 473646 (I'll go add a relevant comment there).
Comment 3 Max Hohenegger CLA 2015-08-05 04:14:26 EDT
> Finish hotfix does not appear to merge to trunk (incorrect).

With 'trunk', do you mean master?
This would be a serious issue. We probably should have a dedicated issue for this.

> So the solution for this issue is to make (at least) start hotfix option available on trunk - though ideally all "start x" options would be available whichever branch is active.

If these command are available in (one of) the CLI implementation, we should implement it as well.
Otherwise, I think this is a minor issue. Personally, I spent very little time on the master branch, hence, having to switch to develop manually is a very minor inconvenience for me.
Comment 4 Max Hohenegger CLA 2015-08-16 05:39:05 EDT
(In reply to Max Hohenegger from comment #3)
> > So the solution for this issue is to make (at least) start hotfix option available on trunk - though ideally all "start x" options would be available whichever branch is active.
> 
> If these command are available in (one of) the CLI implementation, we should
> implement it as well.
> Otherwise, I think this is a minor issue. Personally, I spent very little
> time on the master branch, hence, having to switch to develop manually is a
> very minor inconvenience for me.

I double-checked. On the CLI (1.9.0-dev.33 (AVH Edition)), the start commands are indeed available.
Comment 5 Max Hohenegger CLA 2015-09-09 10:04:13 EDT
I think rather than simply enabling all commands, it would be better to move those commands that require an intermediate step in the Gitflow "state-machine" to a sub-menu.
E.g. when on a feature branch, I would expect to quickly find the "feature finish" or "rebase" operations, and, for example, "start hotifx" somewhere under "other options".
Comment 6 Eclipse Genie CLA 2015-09-27 09:22:02 EDT
New Gerrit change created: https://git.eclipse.org/r/56778
Comment 7 Eclipse Genie CLA 2015-09-27 16:56:19 EDT
Gerrit change https://git.eclipse.org/r/56778 was merged to [master].
Commit: http://git.eclipse.org/c/egit/egit.git/commit/?id=e4993d97de3f2f7a36f0c075227f809c69de8ae7
Comment 8 Matthias Sohn CLA 2015-09-27 16:56:39 EDT
submitted