Jan Tatarik

You're right. I was not aware of the flags' existence, so they are completely ignored by magit-gitflow. Will fix.

Can't reproduce this with empty config and `magit-20190217.2150` / `magit-gitflow-2.2.3`. Is this stil a problem?

As far as I know, both melpa and melpa-stable have the same version, the latest one - 20170929.824 (melpa), 2.2.3 (melpa-stable). What I tried: created a new local repo, committed...

Can you upload the `magit-process` buffer from this little exercise (`$` in the magit buffer)?

OK, this seems to be happening with git-flow `1.12.0`, not sure why yet. `1.10.0` worked fine. Will investigate.

Found the problem. As a temporary workaround, try the following: - open your `.git/config` - find the `[gitflow "prefix"]` section - specify the branch prefix names explicitly, like so ```...

This is caused by https://github.com/petervanderdoes/gitflow-avh/issues/393

Sorry, no idea at the moment. Will look into it.