Avoid spam

[Zomis]

When updating a fork, and on other occasions as well, it is possible that Duga posts > 100 messages in chat, which leads to a whole lot of spam. Avoid such occasions.

Possible solutions:

• [ ] interactively be able to remove queued messages (Administrator only)
• [x] when commits have been pushed, count the number of commits, if they are more than 10 or so, throw away some of the messages

[rubberduck203]

May I suggest setting an upper limit, say 10, and instead of throwing them away, replacing them with something like this.

[Zomis/Rubberduck] ckuhn203 pushed 142 commits to swedish-translation

[Vogel612]

This should be similar to the behavior when pushing already existing commits to a branch after a merge. At some point of simultaneously pushed commits you're better off assuming there was a cross-fork merge than "actual development"