[OPEN-ILS-DEV] Request: include bug numbers in commit messages

Bill Erickson berick at esilibrary.com
Mon Feb 17 13:50:09 EST 2014


+1.

-b


On Mon, Feb 17, 2014 at 1:06 PM, Galen Charlton <gmc at esilibrary.com> wrote:

> Hi,
>
> I'd like to request that we all get in the habit of including bug
> numbers in commit messages -- specifically, in the first line.  Doing
> this will make it easier to work backwards from a commit to the
> description of the bug it fixes without having to fight LP's search
> engine.  It will also make it easier to identify related patches,
> particularly in cases where a patch series does not get pushed all at
> once for whatever reason.
>
> Since essentially all patches [1] go through Launchpad anyway, I don't
> think this will be much of a burden.  For patches that that have
> already been pullrequested, or for cases where a patch gets written
> before a LP ticket is opened, I propose that whoever pushes a patch
> feel free to edit the commit message to add the bug number.
>
> [1] With the obvious exception of patches written during release-cutting.
>
> Regards,
>
> Galen
> --
> Galen Charlton
> Manager of Implementation
> Equinox Software, Inc. / The Open Source Experts
> email:  gmc at esilibrary.com
> direct: +1 770-709-5581
> cell:   +1 404-984-4366
> skype:  gmcharlt
> web:    http://www.esilibrary.com/
> Supporting Koha and Evergreen: http://koha-community.org &
> http://evergreen-ils.org
>



-- 
Bill Erickson
| Senior Software Developer
| phone: 877-OPEN-ILS (673-6457)
| email: berick at esilibrary.com
| web: http://esilibrary.com
| Equinox Software, Inc. / The Open Source Experts
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://libmail.georgialibraries.org/pipermail/open-ils-dev/attachments/20140217/54ae15b3/attachment.htm>


More information about the Open-ils-dev mailing list