-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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(slack): Show culprit in notifications #72980
Conversation
🔍 Existing Issues For ReviewYour pull request is modifying functions with the following pre-existing issues: 📄 File: src/sentry/integrations/slack/message_builder/issues.py
Did you find this useful? React with a 👍 or 👎 |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #72980 +/- ##
===========================================
+ Coverage 46.59% 78.04% +31.45%
===========================================
Files 1873 6624 +4751
Lines 120667 295748 +175081
Branches 21721 50943 +29222
===========================================
+ Hits 56224 230831 +174607
+ Misses 63382 58621 -4761
- Partials 1061 6296 +5235
|
Co-authored-by: Yash Kamothi <yash.kamothi@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we keep testing for slack messages without culprit? right now it seems like we've removed coverage for no culprit messages
Co-authored-by: Cathy Teng <70817427+cathteng@users.noreply.github.com>
There are still tests where there are no culprit blocks – however, in all of them it's currently because the feature flag is off. |
Yay! |
i added the org in the LA group! |
Suspect IssuesThis pull request was deployed and Sentry observed the following issues:
Did you find this useful? React with a 👍 or 👎 |
Just wrapping @olagjo's PR #72587 around a FF so we can quickly turn it on/off.