Hi, I think that checking commit message compliance to commit message guidelines (for example ending the first line with dot) is part of CI jobs, and they will vote -1 if message is wrongly structured.
Maybe there should be separate CI job only for checking commit message? Cheers, Maciej Kwiek On Tue, Jul 28, 2015 at 5:35 PM, Sergii Golovatiuk <sgolovat...@mirantis.com > wrote: > Hi, > > It looks like our CI is not configured to set +1/-1 automatically, when > only commit message is changed. It would be nice to have +1 automatically > when I change Commit Message only instead of waiting hours on CI. It would > save some hardware resources to save some energy and help environment > protection movement. > > -- > Best regards, > Sergii Golovatiuk, > Skype #golserge > IRC #holser > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
