PROJECT DIED; PLEASE SUBMIT ISSUES INTO gitflow-avh

[KES777]

Please submit new issues here

Why you should submit there

The last commit in the repository was on Sep 25, 2012, the last release was on on Feb 14, 2011, it seems this version of git-flow has been abandoned.
Debian and Ubuntu both, have switched to my fork for the package git-flow. If you installed git-flow through their system you are most likely to be using my version already.

If you occasionally submit new issue, please resubmit it by the link above and do not forget to close it at this repo to keep this warning at top
Thank you.

[booc0mtaco]

Thanks for this! I was linked to the older one thru homebrew and didn't realize (btw, if you also use homebrew, you'll want to run brew install git-flow-avh instead of brew install git-flow)

[rachmadaniHaryono]

hi, @KES777 , and (also @petervanderdoes) i just find this issue after researching about git flow. after 6 months this issue is little bit buried and people still posting issue and pr.

is it possible to message these people and maybe close their issue and pr, so this issue can still be on top? also maybe add PR with the same title so people don't put any PR on this repo?

issue:

• Git not working #6375
• patch command #6376
• dead link in readme #6378
• git flow release finish fails when tag prefix is # #6379

pr:

• Making the submodule accessible behind a proxy (via https://) #6372
• Update README.mdown #6373
• Master #6374
• Fix broken URL in README.mdown #6377

[KES777]

Occasionally posting links to those pr/issue you already message them

Sorry, I have not maintain privilege to do that.

If those authors ourselves close their pr/issue then this one will be on top again.

[beyerz]

bumping this as it resolved issues for me

[rachmadaniHaryono]

thanks @beyerz,

unfortunately there are some issue/pr, which are not in the new repo e.g.

issue

• git flow release publish fails if '+' character is included in release name #6381
• Install doc wget and curl have develop branch instead of master #6382
• all commands are taking lot of time #6384
• Support for semver #6386
• SourceTree support #6387
• What is the intended use case for git flow support? #6389
• SVG Request: "GitFlow Badge" like "commitizen" #6390

pr

• add sign flag to feature finish #6385
• Improve git flow init help #6388

[petervanderdoes]

I'm currently on vacation. I did a quick view of the issues and pr's on my phone. When I get back I'll take a deeper look. Send from my phone

…

On Jun 27, 2017, 3:57 AM -1000, rachmadani haryono ***@***.***>, wrote: thanks @beyerz, unfortunately there are some issue/pr, which are not in the new repo e.g. issue • #6381 • #6382 • #6384 • #6386 • #6387 • #6389 • #6390 pr • #6385 • #6388 — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[MTCoster]

My issue (#6387) is not relevant to gitflow-avh, I've already confirmed that the necessary changes have been made there. Should I just close the issue?

[bmcdonnell-ionx]

Is the title of this issue supposed to say, "... SUBMIT ISSUES INTO gitflow-avh"?