Notifyr 4.1 release notes
Release date: 7 Mar 2019
ASK Software is proud to announce the release of Notifyr - Notification for Bitbucket 4.1.0.
Starting today you can specify for which events your notification rules should run! Woohoo!
Prior to this version, the notification hook from Notifyr was triggered for every important event, this didn't allow for more fine-grained notifications.
I received your feedback and added the option to specify these events. The documentation has been updated to reflect which events are recognized.
Get hook notifications on specified events
It is now possible to define for which events a rule should send notifications. Possible events are:
Push | Triggered when code is pushed to a repository, also triggered when editing a file in Bitbucket. |
---|---|
Fork | Triggered when the repository is being forked |
BranchCreate | Triggered when a new branch is created |
TagCreate | Triggered when a new Tag is created |
PullRequestCreate | Triggered when a new Pull Request is created |
PullRequestMerge | Triggered when a Pull Request is merged |
All | Trigger for all the implemented events – default |
If no events are specified the hook is triggered on all the above events.
{ "rules": [{ "events": ["Push", "BranchCreate"], "notifications": [ { "address": "[email protected]" } ] }] }
Send hook notifications to users and groups
Another major change to the hook configuration is the possibility to specify an array of addresses and to use variables!
{ "rules": [{ "notifications": [ { "address": ["[email protected]", "[email protected]"] } ] }] }
Two variables have been added to the json configuration:
${group.<groupname>} | To send a notification to all group members. ie: ${group.bitbucket-users} |
---|---|
${user.<username> | To send a notification to a specifc user |
{ "rules": [{ "notifications": [ { "address": "${group.bitbucket-users}" } ] }] }
Notification on Fork events
Notifyr now sends notifications when a repository is being forked. This can both be specified from the JSON as on a per-user base.
We can't succeed without your feedback, insight, and recommendations for improvement so please keep sending your feedback. Thanks so much!