...
At first none is selected and all events are grayed in those cards. When clicked on any event - bot will remember your new subscription and this event will turn black in a card as a confirmation.
...
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:
...
Additionally our bot supports * matcher for both events and repositories.
Examples
| Code Block | ||||
|---|---|---|---|---|
| ||||
@Atlas subscribe to branch:* in repo1, repo2 |
| Code Block | ||||
|---|---|---|---|---|
| ||||
@Atlas subscribe to pullrequest:*, repo:commit_status_updated in smart-* |
| Code Block | ||||
|---|---|---|---|---|
| ||||
@Atlas unsubscribe from pullrequest:* in * |