Closing features doesn't use --no-ff about gitflow HOT 3 CLOSED

The offending line seems to be this: http://github.com/nvie/gitflow/blob/develop/git-flow-feature#L311

from gitflow.

Yes, that's pretty much on purpose. The whole idea of using --no-ff is to "group together" all commits on a feature branch, to easily see what commits belong together. See the original article for a more detailed explanation.

This implementation prevents single-commit features from using --no-ff, since that explicit merge would add nothing over a fast forward and only make the commit tree more unreadable.

So this behaviour is by design.

from gitflow.

Thanks for the explanation. After I found that line and deduced what it did, I figured that would be the case.

from gitflow.