Skip to content
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

Cleanup in preparation for #2500 #2507

Merged

Conversation

ycombinator
Copy link
Contributor

@ycombinator ycombinator commented Apr 18, 2023

What does this PR do?

This PR performs a bunch of cleanup, as suggested by golangci-lint.

Why is it important?

When #2500 was created, the golangci-lint linter made several suggestions in files touched by the PR, but not on lines related to the changes in that PR. This created unnecessary noise in the PR. To reduce that noise, I've extracted the changes to address those linter suggestions into this separate PR here.

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in ./changelog/fragments using the changelog tool
  • I have added an integration test or an E2E test

@ycombinator ycombinator changed the title Cleanup in preparation for https://github.com/elastic/elastic-agent/pull/2500 Cleanup in preparation for #2500 Apr 18, 2023
@mergify
Copy link
Contributor

mergify bot commented Apr 18, 2023

This pull request does not have a backport label. Could you fix it @ycombinator? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-v./d./d./d is the label to automatically backport to the 8./d branch. /d is the digit

NOTE: backport-skip has been added to this pull request.

@elasticmachine
Copy link
Contributor

elasticmachine commented Apr 18, 2023

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2023-04-18T19:13:13.689+0000

  • Duration: 18 min 3 sec

Test stats 🧪

Test Results
Failed 0
Passed 5535
Skipped 19
Total 5554

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • /package : Generate the packages.

  • run integration tests : Run the Elastic Agent Integration tests.

  • run end-to-end tests : Generate the packages and run the E2E Tests.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@elasticmachine
Copy link
Contributor

elasticmachine commented Apr 18, 2023

🌐 Coverage report

Name Metrics % (covered/total) Diff
Packages 98.529% (67/68) 👍
Files 68.22% (161/236) 👍
Classes 67.785% (303/447) 👍
Methods 54.111% (928/1715) 👍
Lines 39.581% (10496/26518) 👎 -0.038
Conditionals 100.0% (0/0) 💚

@ycombinator ycombinator force-pushed the set-install-base-path-pre-cleanup branch from 0bffaa6 to ff0ca0d Compare April 18, 2023 05:16
@ycombinator ycombinator marked this pull request as ready for review April 18, 2023 05:19
@ycombinator ycombinator requested a review from a team as a code owner April 18, 2023 05:19
@ycombinator ycombinator requested review from AndersonQ and michalpristas and removed request for a team April 18, 2023 05:19
@ycombinator ycombinator marked this pull request as draft April 18, 2023 05:21
@ycombinator ycombinator marked this pull request as ready for review April 18, 2023 20:55
@ycombinator ycombinator merged commit 5fb9985 into elastic:main Apr 19, 2023
@ycombinator ycombinator deleted the set-install-base-path-pre-cleanup branch April 19, 2023 02:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants