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

fix Go Report badge #31399

Merged
merged 1 commit into from
Apr 27, 2022
Merged

fix Go Report badge #31399

merged 1 commit into from
Apr 27, 2022

Conversation

is2ei
Copy link
Contributor

@is2ei is2ei commented Apr 24, 2022

What does this PR do?

This PR updates the Go Report badge since it does not appear correctly now.

Why is it important?

It would be nice to show the current status.

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.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Author's Checklist

  • See the README.

How to test this PR locally

N/A

Related issues

Use cases

N/A

Screenshots

Screen Shot 2022-04-24 at 23 05 24

Logs

@is2ei is2ei requested a review from a team as a code owner April 24, 2022 14:07
@is2ei is2ei requested review from belimawr and faec and removed request for a team April 24, 2022 14:07
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Apr 24, 2022
@cla-checker-service
Copy link

cla-checker-service bot commented Apr 24, 2022

💚 CLA has been signed

@botelastic
Copy link

botelastic bot commented Apr 24, 2022

This pull request doesn't have a Team:<team> label.

@mergify mergify bot assigned is2ei Apr 24, 2022
@elasticmachine
Copy link
Collaborator

elasticmachine commented Apr 24, 2022

💚 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: 2022-04-26T16:39:52.026+0000

  • Duration: 18 min 2 sec

❕ Flaky test report

No test was executed to be analysed.

🤖 GitHub comments

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

  • /test : Re-trigger the build.

  • /package : Generate the packages and run the E2E tests.

  • /beats-tester : Run the installation tests with beats-tester.

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

@belimawr
Copy link
Contributor

Thanks a lot for this PR @is2ei !!

Could you sign the contributor agreement: https://www.elastic.co/contributor-agreement ?

@is2ei
Copy link
Contributor Author

is2ei commented Apr 26, 2022

@belimawr
Thanks. I signed it!

Screen Shot 2022-04-26 at 9 03 15

@belimawr
Copy link
Contributor

/test

@is2ei
Copy link
Contributor Author

is2ei commented Apr 27, 2022

@belimawr
Thanks for your support! It seems all checks have passed.
Could you review this PR when you have time?

@belimawr belimawr merged commit eb15ce4 into elastic:main Apr 27, 2022
@belimawr
Copy link
Contributor

Thank you very much @is2ei !!

kush-elastic pushed a commit to kush-elastic/beats that referenced this pull request May 2, 2022
chrisberkhout pushed a commit that referenced this pull request Jun 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs_team Indicates that the issue/PR needs a Team:* label
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants