Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(notifications): slack request notifications read settings #29718

Merged
merged 4 commits into from
Nov 2, 2021

Conversation

scefali
Copy link
Contributor

@scefali scefali commented Nov 2, 2021

This PR adds logic to check notification settings for the new OrganizationRequestNotification class which uses the APPROVAL type settings. Note, because these notifications are relatively infrequent, we are going to default to allowing Slack notifications instead of forcing the user to opt into them.

@@ -0,0 +1,58 @@
from sentry.models import NotificationSetting, OrganizationMember
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why put this in a new directory instead of with the other slack notif tests?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ceorourke My understanding is that the location of tests should match the file of the main entity being tested

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

On wait, this is not supposed to be in the slack directory...good catch!

@scefali scefali merged commit 6dede73 into master Nov 2, 2021
@scefali scefali deleted the feat/slack-request-notifications-read-settings branch November 2, 2021 22:24
@github-actions github-actions bot locked and limited conversation to collaborators Nov 18, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants