Roberto,

Unrelated to bzr and the current issue, but for your question about git, see:

http://git-scm.com/book/en/Customizing-Git-Git-Hooks:

"The commit-msg hook takes one parameter, which again is the path to a temporary file that contains the current commit message. If this script exits non-zero, Git aborts the commit process, so you can use it to validate your project state or commit message before allowing a commit to go through."

Regards,

Jeremy


On Fri, Aug 9, 2013 at 10:02 AM, Roberto Spadim <roberto@spadim.com.br> wrote:
hi, IMHO,

yes with hooks is possible, 
but here the main problem is add the issue number at commit description
developers solve some issues and forget about add the issue tracker number to comment

here (at my projects) we parse the commit with a php script hook, that found strings like "#SMM-1234567"  (#SMM is the project name, 1234567 is the issue id), after founding the script link the commit to issue via rest api
The problem occur when there's no #SMM string in commit
There's no "don't commit" hook at git, at least i didn't see this here, if anyone know if there's a "don't commit" feature at bzr or git :) please share this information :)
The only problem of a "most have issue tracker string", is when developers do some new features not tracked by issue tracker



_______________________________________________
Mailing list: https://launchpad.net/~maria-developers
Post to     : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp