-
Notifications
You must be signed in to change notification settings - Fork 896
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
Pin markdownlint-cli version and apply fixes #2320
Merged
bogdandrutu
merged 2 commits into
open-telemetry:main
from
dynatrace-oss-contrib:fix-markdownlint
Feb 7, 2022
Merged
Pin markdownlint-cli version and apply fixes #2320
bogdandrutu
merged 2 commits into
open-telemetry:main
from
dynatrace-oss-contrib:fix-markdownlint
Feb 7, 2022
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
arminru
added
the
editorial
Editorial changes only (typos, changelog, ...). No content-related changes of any kind.
label
Feb 7, 2022
This was referenced Feb 7, 2022
yurishkuro
approved these changes
Feb 7, 2022
MrAlias
approved these changes
Feb 7, 2022
bogdandrutu
approved these changes
Feb 7, 2022
Thanks for the fix. |
chalin
reviewed
Feb 15, 2022
- If schema_url field is non-empty both in Resource* message and in the | ||
contained InstrumentationLibrary* message then the value in | ||
InstrumentationLibrary* message takes the precedence. | ||
- If schema_url field is non-empty both in Resource\*message and in the |
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.
This erased the space between Resource* and message. I don't believe that was intended, right?
carlosalberto
pushed a commit
to carlosalberto/opentelemetry-specification
that referenced
this pull request
Oct 31, 2024
* Pin markdownlint-cli version * Apply markdownlint fixes
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
editorial
Editorial changes only (typos, changelog, ...). No content-related changes of any kind.
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.
Some breaking changes in the most recent markdownlint-cli version (see https://github.com/igorshubovych/markdownlint-cli/releases) cause all current checks to fail. This PR pins its version so this does not happen again and applies the fixes proposed by markdownlint (inconsistent emphases within one file and unescaped asterisks).