Yep, out of the box Gerrit commit hooks cannot block new patches from being uploaded. An alternative would be to immediately set the vote on the patchset to Code-Review to -2 if the commit message doesn't match what you want. The hook script for something like that can be found here: https://gerrit.googlesource.com/gerrit/+/master/contrib/check-valid-commit.py
-Khai On Tue, Mar 24, 2015 at 12:27 PM, Darragh Bailey <[email protected]> wrote: > I believe the its-* plugins for gerrit could handle this for you, recently > someone mentioned on the repo mailing list that you can even exclude > branches from the requirement. > > I'd suggest asking there directly if you haven't already. > > Darragh > On 23 Mar 2015 22:17, "Jeremy Stanley" <[email protected]> wrote: > >> On 2015-03-23 12:00:26 +0530 (+0530), Vinay Mahuli wrote: >> > I need info on where to make this change in a similar way how >> > Change-Id is checked/validated. >> >> "Require Change-Id in commit message" is a project-specific setting >> built into Gerrit by default. >> >> <URL: >> https://gerrit-review.googlesource.com/Documentation/project-configuration.html#_require_change_id >> > >> >> Something similar may be possible by writing a Gerrit plug-in or a >> hook script, but it will almost certainly use a different mechanism >> as it won't be implemented directly in the Gerrit codebase as a >> built-in feature. >> -- >> Jeremy Stanley >> >> _______________________________________________ >> OpenStack-Infra mailing list >> [email protected] >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra >> > > _______________________________________________ > OpenStack-Infra mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra > >
_______________________________________________ OpenStack-Infra mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
