Uploaded image for project: 'Sourcetree for Windows'
  1. Sourcetree for Windows
  2. SRCTREEWIN-1394

Switch to git-flow-avh

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Fixed
    • 2.2.4.0
    • Git
    • Standard OS X app, 1.6.2.2

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Including Git Flow is awesome, but would it be possible to use the Git Flow AVH fork (https://github.com/petervanderdoes/gitflow)?

      The original Git Flow hasn't been updated in nearly a year now as where the AVH fork is constantly seeing new releases containing both fixes and features.

      It functions exactly the same and should be a drop in replacement.

        1. git-flow-preview.png
          git-flow-preview.png
          7 kB

            [SRCTREEWIN-1394] Switch to git-flow-avh

            Emanuel Virca added a comment -

            When will the UI for a "bugfix" branch be added to the UI?

            Emanuel Virca added a comment - When will the UI for a "bugfix" branch be added to the UI?

            Ilan Cohen added a comment -

            I checked and I have the AVH version of GitFlow, and everything looks fine.

            But when will the UI for a "bugfix" branch be added to the UI?

            Ilan Cohen added a comment - I checked and I have the AVH version of GitFlow, and everything looks fine. But when will the UI for a "bugfix" branch be added to the UI?

            jbcodes added a comment -

            Thanks, Mike. That did help. However, I don't know how many people will have to delete the gitflow_local folder. Would be better to do this automatically on update... or make some kind of button "update git-flow" inside application... or at least some hint "hey, you should definitely delete the gitflow_local folder".

            Oh, and there is one more, very tiny issue - the preview. It still shows the old workflow.

            Anyway, thanks for your work. Finally, a proper git-flow in SourceTree! 

            jbcodes added a comment - Thanks, Mike. That did help. However, I don't know how many people will have to delete the gitflow_local folder. Would be better to do this automatically on update... or make some kind of button "update git-flow" inside application... or at least some hint "hey, you should definitely delete the gitflow_local folder". Oh, and there is one more, very tiny issue - the preview. It still shows the old workflow. Anyway, thanks for your work. Finally, a proper git-flow in SourceTree! 

            Mike Corsaro (Inactive) added a comment - - edited

            Hello! We shipped with AVH in v2.2.1. It sounds like you already had git-flow installed, so it didn't overwrite it with the new version. You can check the installed version by opening:
            "C:{USERNAME}\AppData\Local\Atlassian\SourceTree\gitflow_local\gitflow\README.md"

            The top of the file should say: git-flow (AVH Edition)

            If it doesn't say that, then you can close Sourcetree, delete the "gitflow_local" folder, and then restart Sourcetree. Hitting the "Flow" button will re-install git-flow.

            Mike Corsaro (Inactive) added a comment - - edited Hello! We shipped with AVH in v2.2.1. It sounds like you already had git-flow installed, so it didn't overwrite it with the new version. You can check the installed version by opening: "C:{USERNAME}\AppData\Local\Atlassian\SourceTree\gitflow_local\gitflow\README.md" The top of the file should say: git-flow (AVH Edition) If it doesn't say that, then you can close Sourcetree, delete the "gitflow_local" folder, and then restart Sourcetree. Hitting the "Flow" button will re-install git-flow.

            jbcodes added a comment - - edited

            "Fixed"?

            This is weird. It appeared in release notes (v. 2.2.1.0)... but I checked it and it doesn't work like the AVH version! The release is merged into both develop and master branches, instead of merging into master, tagging and merging the tag back to deveop.

            So, I hope it really is fixed, but not yet released!

            jbcodes added a comment - - edited "Fixed"? This is weird. It appeared in release notes (v. 2.2.1.0)... but I checked it and it doesn't work like the AVH version! The release is merged into both develop and master branches, instead of merging into master, tagging and merging the tag back to deveop. So, I hope it really is fixed, but not yet released!

            Dino Korah added a comment -

            Any news on the progress of this? Really looking forward to it!

            Dino Korah added a comment - Any news on the progress of this? Really looking forward to it!

            mcahornsirup added a comment -

            This is really (not) funny. AVH seems to be the way to go... it would be pretty cool if SourceTree could adopt to the git-flow version used (bugfix/supprt UI-Elements etc.)
             

            mcahornsirup added a comment - This is really (not) funny. AVH seems to be the way to go... it would be pretty cool if SourceTree could adopt to the git-flow version used (bugfix/supprt UI-Elements etc.)  

            jbcodes added a comment - - edited

            It has been almost 4 years since previous issue on switching to gitflow AVH (https://jira.atlassian.com/browse/SRCTREE-1762).

            Now this issue even has "needs verification" status. And this doesn't look too good. 

            jbcodes added a comment - - edited It has been almost 4 years since previous issue on switching to gitflow AVH ( https://jira.atlassian.com/browse/SRCTREE-1762 ). Now this issue even has "needs verification" status. And this doesn't look too good. 

            JDFagan added a comment -

            You need to up the priority on this - I use gitflow every day and not addressing this is becoming a pain point.  Pain points lead to moving to other solutions.  I'd rather stay with SourceTree so am asking for you to embed gitflow-avh which was updated only 2 months ago vs. the stagnant gitflow original from over 5 years prior.  Should be easy to do with big impact to your loyal users who help spread use of your product.

            JDFagan added a comment - You need to up the priority on this - I use gitflow every day and not addressing this is becoming a pain point.  Pain points lead to moving to other solutions.  I'd rather stay with SourceTree so am asking for you to embed gitflow-avh which was updated only 2 months ago vs. the stagnant gitflow original from over 5 years prior.  Should be easy to do with big impact to your loyal users who help spread use of your product.

            Michael Mallett added a comment -

            Git Flow has not been updated in 4 years. It's actually ridiculous that you still don't allow movement onto the upto date version. How long is this going to go on for?

            Michael Mallett added a comment - Git Flow has not been updated in 4 years. It's actually ridiculous that you still don't allow movement onto the upto date version. How long is this going to go on for?

              mcorsaro Mike Corsaro (Inactive)
              c092763da3c7 C Fraire
              Votes:
              89 Vote for this issue
              Watchers:
              52 Start watching this issue

                Created:
                Updated:
                Resolved: