Hi, I add another look and I think I fixed the off-by-one issue.
Let me know if this is fixed for you. - Sylvain On Mon, Jan 03, 2011 at 08:43:46PM +0100, Nils Gey wrote: > Hello, > > our GIT Ciabot makes more problems than it benefits. > It always is -1 commits off, the situation has not changed. But recently it > began to refuse git pushes because of some CIA error. I guess this is related > to the CIA system itself, but its still getting on my nerves. > > If you don't know how to correct that the CIA bot is off -1 it would be nice > if you can remove the cia hook from our project: GNU Denemo. > > greetings, > > Nils, > http://www.denemo.org > > > On Wed, 1 Sep 2010 23:43:16 +0200 > Sylvain Beucler <b...@gnu.org> wrote: > > > Hi, > > > > > 1) I meant which git hook does the ciabot call? post-receive I guess, but > > > I don't know if there are any alternatives. > > > > 'update': > > > > r...@vcs-noshell:/srv/git# cat denemo.git/hooks/update.d/ciabot > > #!/bin/bash > > refname=$1 > > oldhead=$2 > > newhead=$3 > > exec /usr/src/git/contrib/ciabot/ciabot.py ${refname} $(git rev-list > > ${oldhead}..${newhead} | tac) > > > > The documentation in ciabot.py suggests doing it that way. > > > > > > > 2) It seems, that the script works on per received push basis, not > > > commit. That means if we push several commits at once CIA just takes > > > this as on message. (And then shows the last one before that pack :) > > > ). Any chance to let cia show every single commit, not only one per > > > push? > > > > Well as far as I'm concerned multiple commits per push do work in > > savane.git. Then again, that particular repository also don't have > > the "one-commit-late" issue. > > > > -- > > Sylvain > >
