branches filtering support

[Adam Adamaszek]

Our team members use git branches a lot: 1/ to run remote precommit builds, 2/ to do spikes, features etc. 3/ for complicated merges

With current state of things this results in a lot of emails sent, so everyone starts ignoring those notifications.

Would it be possible to add a configuration entry, say "branches", that would do white- or black-list filtering of branches that should send emails, and those that should not?

For example, i would say:

+refs/heads/master +refs/heads/release/*

And no emails would be sent for other than those.

[Adrian Milliner]

I too need this. Any site using something like gitflow will get way too much email and will end up blocking it, as such we can't use this without a basic branch filtering.

The code as-is seems to do branch extraction at the message formatting stage and this involves executing git commands. Some refactoring might be in order to pre-extract this and cache it should it be needed by white/blacklisting.

[Marc Vanbrabant]

Hi,

I will try and pick this up in a next version. If you do feel like contributing I'll gladly accept a PR.

Kind regards M.