-
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
Removing double punctuation in PR message #164
Conversation
Codecov Report
@@ Coverage Diff @@
## main #164 +/- ##
=======================================
Coverage 98.34% 98.34%
=======================================
Files 374 374
Lines 28144 28144
=======================================
Hits 27678 27678
Misses 466 466
Flags with carried forward coverage won't be shown. Click here to find out more.
This change has been scanned for critical changes. Learn more |
Codecov Report
@@ Coverage Diff @@
## main #164 +/- ##
=======================================
Coverage 98.38% 98.38%
=======================================
Files 348 348
Lines 27648 27648
=======================================
Hits 27201 27201
Misses 447 447
Flags with carried forward coverage won't be shown. Click here to find out more.
|
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #164 +/- ##
=======================================
Coverage 98.38% 98.38%
=======================================
Files 348 348
Lines 27648 27648
=======================================
Hits 27201 27201
Misses 447 447
Flags with carried forward coverage won't be shown. Click here to find out more.
|
Accidental double punctuation highlighted by @chadwhitacre codecov/feedback#54 (comment)
Legal Boilerplate
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. In 2022 this entity acquired Codecov and as result Sentry is going to need some rights from me in order to utilize my contributions in this PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.