-
Notifications
You must be signed in to change notification settings - Fork 10
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
Failed check and status messaging in comment, part II #1023
Conversation
9dc9f9b
to
b7348ce
Compare
✅ All tests successful. No failed tests were found. 📣 Thoughts on this report? Let Codecov know! | Powered by Codecov |
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.
LGTM
codecov.yml
Outdated
@@ -7,7 +7,7 @@ component_management: | |||
default_rules: | |||
statuses: | |||
- type: project | |||
target: auto | |||
target: 99 |
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.
Was this for testing? Do we want to leave it like so?
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.
i wanted to trigger the help text im adding in this pr, but i changed this in a separate commit after the first pr comment already happened, so i think the comment didn't update with my helper text. I'll manipulate it some more...
owner.plan == BillingPlan.team_monthly.value | ||
or owner.plan == BillingPlan.team_yearly.value | ||
): | ||
owner_plan = PlanService(owner) |
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.
nice 👍
9d9d277
to
07be913
Compare
5140b65
to
283a406
Compare
❌ 1 Tests Failed:
View the top 1 failed tests by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
❌ 1 Tests Failed:
View the top 1 failed tests by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
Codecov ReportAttention: Patch coverage is
✅ All tests successful. No failed tests found.
Additional details and impacted files@@ Coverage Diff @@
## main #1023 +/- ##
=======================================
Coverage 97.71% 97.71%
=======================================
Files 458 458
Lines 37072 37138 +66
=======================================
+ Hits 36224 36289 +65
- Misses 848 849 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Codecov ReportAttention: Patch coverage is ✅ All tests successful. No failed tests found.
📢 Thoughts on this report? Let us know! |
7c99a5a
to
9634837
Compare
55997ae
to
94a506d
Compare
…o other notifiers
…user has defined a `target`
94a506d
to
bcef3bc
Compare
Suspect IssuesThis pull request was deployed and Sentry observed the following issues:
Did you find this useful? React with a 👍 or 👎 |
when user has:
patch checks notifier OR patch status notifier
AND
comment notifier
AND
has defined a
target
in their codecov ymlAND
the patch check/status fails
THEN
add some helper text to the comment notifier to point out that the check/status failed and that they can change their
target
.codecov/engineering-team#1626