On Friday 17 May 2013 12:40:10 Derek Atkins wrote: > Geert Janssens <janssens-ge...@telenet.be> writes: > > This will again require developers to think upfront about their commit > > messages. In itself a good thing, but harder to enforce. I refer back > > here to our long discussion on a branching strategy in git, in which > > we also had some potential workflow improvements that depended on > > every developer adhering to it. > > I wonder if there is any way we could get gitolite to enforce the > process/standards we create? > We can't enforce everything, but I believe it's at least possible to enforce the format of the commit message we want. Each commit is passed through our commit hooks on the server. In these commit hooks we can define the basic requirements for our commit messages so they become useful for later automatic processing later on.
We can gradually improve on this based on real experience. > > -derek Geert _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
