Bulk subscribing and unsubscribing from events

When having heavy count of Bitbucket repositories then @Atlas configure subscriptions may not be the quickest way to configure subscriptions in your room. For such cases you may want to use following commands

Type @Atlas subscribe to [events] in [repositories] to bulk subscribe subscribe to specified events in given repositories.

Type @Atlas unsubscribe from [events] in [repositories] to bulk subscribe unsubscribe from specified events in given repositories.

Our bot supports following events:

Event	Notes

Event	Notes
pullrequest:created	Generate card when pull request is created in a given repository.
pullrequest:approved	Generate card when someone approves a pull request in a given repository .
pullrequest:unapproved	Generate card when some cancels his approbal for pull request in a given repository.
pullrequest:rejected	Generate card when someone rejects a pull request.
pullrequest:fulfilled	Generate card when pull request is being merged.
pullrequest:commented	Generate card when someone comments a pull request
pullrequest:updated	Not yet implemented.
repo:commit_status_created	Generate card when pipeline build is started.
repo:commit_status_updated	Generate card when pipeline build finished.
branch:created	Generate card when branch is being created. This event is supported only in GIT repositories.
branch:updated	Generate card when there is a push to branch. This event is supported only in GIT repositories.
branch:deleted	Generate card when branch is deleted. This event is supported only in GIT repositories.

Additionally our bot supports * matcher for both events and repositories.

Examples

Subscribe to all branch events in two repositories

@Atlas subscribe to branch:* in repo1, repo2

Subscribe to pull request events, finished builds and all repositories prefixed as 'smart-'

@Atlas subscribe to pullrequest:*, repo:commit_status_updated in smart-*

Unsubscribe from pull request events in all repositories

@Atlas unsubscribe from pullrequest:* in *