Allow to send notifications and to skip bumping VERSION_FILE

[exAspArk]

Hi,

We currently use git-flow-hooks to send notifications in our Slack channel and Hipchat room. It's very useful to track release and hotfix changes, especially for those who don't work with repository directly. So we also decided to specify versions manually as it is quite easy to see all previous versions in a messenger.

I thought it might be useful for someone else.

[jaspernbrouwer]

Hi there! Finally you might think 😉

Allowing to not use a version-file is actually a cool idea, and I'd like to integrate that!

Sending notifications is also cool, but I'm not sure which way to go on that. These kind of features have been asked before, and I've seen some forks with nice additions in that regard, but the actual implementation has always been rather straightforward. Not that that's a down-side per se, but I envision a more plugin-like structure where users can add these in a more uniform way. Unfortunately that would take some time and testing to implement.

So, if I may be so blunt, I have two questions:

1. Can you split this PR up into 2 PRs? 1 containing the functionality to disable the version-file (which I will merge for sure!). The other ...
2. Can you add a section to the readme where you point to you own fork, where you add the sending notifications functionality? This will give me some room to think about / implement a more robust structure, while others are pointed to the right location if they want it now 😄 .

[exAspArk]

@jaspernbrouwer glad to hear from you 😸

Thanks for your feedback. Supporting a plugin-like structure sounds like a great idea!

I've opened 2 separate PRs:

1. Allow to skip writing to the VERSION_FILE #20 – Allow to skip writing to the VERSION_FILE
2. Add link to the fork which sends notifications to Slack / HipChat #21 – Add link to the fork which sends notifications to Slack / HipChat

Closing this PR then