git/list[1] front-page[2] threads[3] people[4] search[5] about
 

ciabot scripts and merge flood prevention

From
Joey Hess <joey@kitenet.net>
Date
Apr 24, 2010, 15:05 UTC
Message-ID
<20100424150511.GA7318@gnu.kitenet.net>

There's a problem with the old ciabot scripts, and I think also the v3 versions, when two published branches are merged. In this case, ciabot reports all the changes twice, once when they're first committed to the first branch, and a second time when the first branch is merged into the second. This can unleash a flood of redundant commit messages that wipes out conversation in any poor irc channel that has CIA in it. I've generated floods that lasted up to 15 minutes.

I document the problem and one solution here. There's also a link to the hook script Gnome is using, based on the same method. http://kitenet.net/~joey/blog/entry/lazyweb:_git_cia_hooks/ Maybe this could be built into the ciabot scripts?

(BTW, in both scripts, the example of git-rev-list ... | tac could perhaps more efficiently be written as git-rev-list --reverse ...)

-- 
see shy jo
Next: Eric Raymond
Message 1 of 2 in “ciabot scripts and merge flood prevention”
  1. Joey HessApr 24, 2010
  2. Eric RaymondApr 24, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.