This is a great and needed feature not just for git flow but with many repo operations including commit (shared message), create branch, rename branch, delete branch, rebase head to....

Other feature requests exist with this idea.  Some I found (searching in userecho is very limited :(  ) are:
https://smartgit.userecho.com/en/communities/1/topics/292-multiple-commit

https://smartgit.userecho.com/en/communities/1/topics/956-multiple-branch-renaming

https://smartgit.userecho.com/en/communities/1/topics/1004-allow-repo-actions-on-selected-groups

https://smartgit.userecho.com/en/communities/1/topics/722-git-rebase-head-to-fetched-option-on-multiple-selected-repos-or-repo-group

Yes, I stash them as my workaround and then unstash when complete.  Not difficult, but surprising it forces me to.  My guess is it is a protective measure.

Is this request complete?  We can select multiple repos and push/fetch/pull them.

My preference is a keyboard shortcut (e.g. Alt-q) and not particular as to which UI component it maps to.  Reviewing them, context menu is less invasive; hamburger menu doesn't work well as is about messages, and a button would stand out on the UI.

May we understand why a manually invoked format option will not work?  Do you mean technically?  Is there also a difference between the Commit "dialog" vs Commit "view".

What options exist that will technically work?

Agreed.  While auto-formatting while typing is really nice, I'm very happy with a manually invoked format option.

Thanks for the reply Thomas.

Do you mean internally/technically or do you mean from a user-feature interaction?

Wondering if this feature is in release plans and forthcoming?  Manually formatting a commit message with newlines is a time waster!

The commit line length guides are set to the Git commit standards.  Changing them is "kind of worthless" as then you violate the Git standard.  What use case do you have that requires violating the standard?

No, didn't realize I'd have to do that.  That works, thanks again.