Fixes typo in log message #17897
Merged
Fixes typo in log message #17897
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ycombinator
added
the
Team:Services
|
Pinging @elastic/integrations-services (Team:Services) |
ycombinator
added
v7.7.1
v7.8.0
v8.0.0
needs_backport
ycombinator
force-pushed
the
fb-fix-typo
branch
from
eeb03ea
to
c239347
Compare
ycombinator
force-pushed
the
fb-fix-typo
branch
from
c239347
to
90f8a62
Compare
This was referenced Apr 25, 2020
ycombinator
added a commit
that referenced
this pull request
Apr 27, 2020
ycombinator
added a commit
that referenced
this pull request
Apr 27, 2020
leweafan
pushed a commit
to leweafan/beats
that referenced
this pull request
Apr 28, 2023
* Fixes typo in log message * Adding CHANGELOG entry
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Fixes a small typo in a log message
Why is it important?
So the log message is not confusing.
Checklist
My code follows the style guidelines of this projectI have commented my code, particularly in hard-to-understand areasI have made corresponding changes to the documentationI have made corresponding change to the default configuration filesI have added tests that prove my fix is effective or that my feature worksCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.