address #56 and change commit formatting to look more like the git hook

[Dav1dde]

This removes the omit phase options, it will always be the shown.
Adds what was requested in #56 (filtering for status), also changing the the BooleanFields to SelectMultipleField.

[TkTech]

Thanks for these changes, but I think it's a good idea to start requiring at least basic tests (using nosetest), especially since I have no Jenkins setup floating around to test. I'm thinking /tests, /tests/data/. /tests/data/ will have payload examples used in the tests. For the hooks, the tests are simple. Make a fake request, check the response.

[TkTech]

Thoughts?

[Dav1dde]

I can definitely add tests to an existing infrastructure, since I never really worked with one of the bigger unittesting-frameworks apart from the std. unittest, I don't really know how that would look.

I imagine the tests (for Hooks) would require an easy way of influencing the parameters of handle_request, if that is in place, adding tests should be pretty easy and fast.

PS: I fixed the comment-issue and rebased the commits

[Dav1dde]

So what is the current state? Tests?