We use precommit hooks with our repositories to ensure we can tie commits to the appropriate ticket in our bugtracking system. However, none of the "automatic" commits (starting with init) that hgflow generates will pass muster, because they are missing the correct text. Since certain hgflow commands generate multiple commits, I cannot rely on manually reissuing the commit after the fail to fix this.
From a design point of view, there seems like two ways to handle this:
1) Append/prepend user supplied --message text to whatever it was that hgflow would normally use.
2) Replace the hgflow text with the contents of --message (thus requiring the user to include relevent information in their message).
I think #1 is much better, since it would always mean the relevant merge/branch messages that hgflow emits are included in every commit message. This corresponds to how you can add the --log option to graft to get the source hash added automatically to the original commit message.
On the other hand, I suspect that
#2 would be simpler to implement, but more prone to user error.
Thoughts? I'm probably going to try to get this working on my own, so you may get a pull request (against v0.95.0 I assume would be best).