-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
✨ feat(scm): add environment infomation to suspect commit prs #93025
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
Conversation
title=issue.title, | ||
subtitle=self.format_comment_subtitle(issue.culprit), | ||
subtitle=self.format_comment_subtitle(issue.culprit or "unknown culprit"), |
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.
turns out culprit is falsy
return f" Environment: *({environment.name})*" | ||
except Exception as e: | ||
# If anything goes wrong, just continue without environment info | ||
logger.info( |
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.
not error
because i don't think a sentry issue is warranted. this can happen if user doesn't set up environments as well
Codecov ReportAttention: Patch coverage is ✅ All tests successful. No failed tests found.
Additional details and impacted files@@ Coverage Diff @@
## master #93025 +/- ##
========================================
Coverage 88.03% 88.04%
========================================
Files 10335 10337 +2
Lines 596828 597013 +185
Branches 23196 23196
========================================
+ Hits 525432 525613 +181
- Misses 70937 70941 +4
Partials 459 459 |
0353526
to
75e7993
Compare
b15741d
to
a3fcc55
Compare
This pr adds environment information to pr comments.
there isn't a clean way to fetch the environment for a group since there can be many environments associated for a group, but when we open the issue details page, it defaults to opening the
recommended_event
(which will also be thelatest_event
for low frequency groups.this made it an ideal candidate to grab the event for, then fetch its environment and show it in the pr comment. this should address the main pain point since errors in dev will be relatively new and be the recommended event
closes ECO-94