Notifications overview

This page describes the behavior of notifications in Secure Source Manager. For instructions on how to set up notifications, see Set up notifications.

Secure Source Manager notifications are disabled by default. When enabled, notifications are sent to your Secure Source Manager login email.

Limitations

The following limitations apply to email notifications in Secure Source Manager:

  • Email notifications aren't available for Workforce Identity Federation users.
  • The email address that notifications are sent to is the same as your Secure Source Manager login email address, and can't be changed.

Events that trigger notifications

The following issue events and pull request events can trigger notifications in Secure Source Manager when notifications are enabled:

Issues:

  • An issue is created
  • An issue is assigned
  • An issue has a new comment
  • An issue is closed
  • An issue is reopened

Pull requests:

  • A pull request is created
  • A pull request is assigned
  • A pull request has a new comment
  • A pull request is approved
  • A pull request is merged
  • A pull request is rejected
  • A pull request is closed
  • A pull request is reopened

Notifications for participants

You can choose to be notified for events in issues and pull requests that you are a participant of.

For example, if you're the author or assignee of a pull request, you're a participant in that pull request, and events in that pull request send you notifications if you have enabled notifications for pull requests.

The following list gives some examples of actions that make you a participant in an issue or pull request:

  • You're the author of the pull request or issue.
  • You're CC'd on the pull request or issue.
  • You comment on the pull request or issue.
  • You're mentioned in the pull request or issue.

Notifications for non-participants

After enabling notifications, you can choose to receive notifications from events in issues or pull requests that you're not participating in by watching a repository. When a repository is watched, notifications are sent for all enabled events, even if you're not a participant in the issue or pull request where the event occurred.

For example, if user1@example.com has enabled notifications for pull requests, and watched a repository, and user2@example.com creates a pull request in that repository, a notification is sent to user1@example.com.

Repositories are not watched by default, except by the repository creator. When you create a new repository, that repository is watched by default and notifications are sent to you for events if you have notifications enabled.

What's next