[JdeRobot] Good practices into github commits

[Victor Arribas]

I will try to do this.

But please, no one use Fix, fixes close or closes #<number> because this
lead in a bad traking for github:
> First commit with this text will close issue and be tracked by github
> Any other commit will be silently omited by github

By the way, perhaps you need a better tool (or at least look) to review git
log.
You can try logmerges:
  https://github.com/varhub/my-gitconfig/blob/master/.gitconfig#L8-9
  It filters log to only present you merges into HEAD (==pull request).
Experimental!

PS: I cant remember what verbs are hooked by github to automatize several
stuff like issue closing.

2016-01-11 20:06 GMT+01:00 Francisco Rivas <franciscomiguel.rivas en urjc.es>:

> Hi all,
>
> we have a new "good practice" that we want to introduce into our git
> protocol. Please, include the issue number before each commit so we can
> trace the solution of the issue in a better way.
>
> If you want to commit some changes related to the issue 123 you should
> include #123 into the text of your commit.
>
> Don't care if you have to commit multiple changes into a single issue just
> put the same issue number into all the commits.
>
>
> thanks to all,
> Fran.
>
> --
> ------------------------------------------------------------------
> Linkedin: linkedin.com/in/fmrivas
>
>
> _______________________________________________
> Jde-developers mailing list
> Jde-developers en gsyc.es
> http://gsyc.escet.urjc.es/cgi-bin/mailman/listinfo/jde-developers
>
>
------------ próxima parte ------------
Se ha borrado un adjunto en formato HTML...
URL: http://gsyc.escet.urjc.es/pipermail/jde-developers/attachments/20160112/80821d93/attachment.htm