This is a known issue: http://logicalawesome.lighthouseapp.com/projects/8570/tickets/341-hooks-are-sent-duplicate-commits In short, when a hook is called it gets passed all commits that are "new" to the branch, instead of new to the repo. Perhaps the twitter service should be changed to send one tweet per push instead of per commit.
On Tue, Sep 16, 2008 at 2:12 PM, Jorge Ortiz <[EMAIL PROTECTED]> wrote: > > The Lift project has a repo (dpp/liftweb) that publishes updates to > Twitter. Most development happens on the 'master' branch, and commits > to this branch get published to Twitter (this is great). We also have > a parallel 'scala-snapshot' branch that makes some minor changes to > keep compatibility with a future release of the Scala language. > Periodically, I merge changes from 'master' into 'scala-snapshot' to > make sure everything is still ok, but I don't want to merge changes > from 'scala-snapshot' into 'master' until a new release has been made > to the Scala language. Unfortunately, whenever I merge 'master' into > 'scala-snapshot' and push those changes to Github, Github re-tweets on > all the commits that have happened to 'master' since the last merge > with 'scala-snapshot'. This can cause quite a storm of tweets which > are really uninformative (and they are changes that may have happened > a while ago and have already been tweeted anyway). > > Is there a way to make Github only tweet on commits to a certain > branch? Or to only tweet once on unique commits? > > Thanks, > > --j > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "GitHub" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/github?hl=en -~----------~----~----~----~------~----~------~--~---
