Is this repository dead?

[nvaken]

Seems to me that this repository is dead (see the last commit being from 2012), though all contributors are very much alive (see the fairly frequent pull requests). Is there any new leading repository for this one that we could be following? There are too many forks to even display in Github.

• Is @nvie still watching this repository?
• Should we define a new lead repository / owner? Or is there one already?
• If so, is there any way we can reference to a new repository in the readme? (I think not without @nvie)

[corbinu]

Not sure why @nvie is ignoring it but your answers are in this PR

https://github.com/nvie/gitflow/pull/419/files

[petervanderdoes]

As mentioned in the referenced pull request git-flow (AVH Edition) is still maintained.

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.

Checkout the changelog for more information about bugfixes and new features implemented in my fork.

[internalsystemerror]

I can vouch for AVH Edition, many issues fixed, some new features, and active development.

[bentcoder]

$ git flow release finish 0.1.0
Switched to branch 'master'
Your branch is up-to-date with 'origin/master'.
Merge made by the 'recursive' strategy.
 one.txt | 1 +
 1 file changed, 1 insertion(+)
 create mode 100644 one.txt
Deleted branch release/0.1.0 (was c708397).

Summary of actions:
- Latest objects have been fetched from 'origin'
- Release branch has been merged into 'master'
- The release was tagged '0.1.0'
- Release branch has been back-merged into 'develop'
- Release branch 'release/0.1.0' has been deleted

Based on my experience, there is no evidence of claim Release branch has been back-merged into 'develop' in @nvie 's unmaintained git-flow. As a result, GitHub was asking me to create a pull request after pushing master branch because release was never merged in to develop.

SOLUTION:

Use @petervanderdoes 's git-flow-avh version.

+1 @petervanderdoes for picking it up.
-1 @nvie for dumping it just like that!

[KES777]

Yes, it is dead. #6370