-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[chore] clean up revive configuration #6353
base: main
Are you sure you want to change the base?
Conversation
/cc @pellared |
7d7a19f
to
44c5f53
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #6353 +/- ##
=======================================
- Coverage 81.8% 81.8% -0.1%
=======================================
Files 283 283
Lines 24900 24900
=======================================
- Hits 20387 20386 -1
- Misses 4109 4110 +1
Partials 404 404 |
44c5f53
to
d5d355b
Compare
7f3d064
to
a954f93
Compare
Signed-off-by: Matthieu MOREL <[email protected]>
a954f93
to
54b2163
Compare
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.
Side note from https://github.com/open-telemetry/opentelemetry-go/blob/main/CONTRIBUTING.md#how-to-send-pull-requests:
Avoid rebasing and force-pushing to your branch to facilitate reviewing the pull request. Rewriting Git history makes it difficult to keep track of iterations during code review. All pull requests are squashed to a single commit upon merge to
main
.
Description
Following #6273 (review)
This clean up revive configuration