Really like the level of control the new Control Freak plugin gives. Amazing job!
I did run into an issue though with the
Authorship Policy. I enabled both
Author must be a valid Bitbucket User and
Committer must be a valid Bitbucket User and got the error:
remote: remote: Control Freak remote: ----- remote: Commit *** rejected: bad committer metadata. remote: Committer "Marijn van Zon <***email***>" does not exactly match remote: a Bitbucket user record. The closest match is: remote: remote: "*** <>" remote:
It looks like Control Freak tries to match the git
user.name against the Bitbucket username instead of the real name.
This happens both when trying to use Bit-booster's Squash in the Bitbucket UI (even when squashing commits of which both committer and author was someone else) and when trying to push to the repository.
Currently I'm using "Yet Another Commit Checker" to validate that both the
user.name matches the Bitbucket user's (real) name and the
user.email matches the Bitbucket user's email. If Control Freak can handle this it would be nice because then we can get rid of YACC :).
Marijn van Zon.