infra: Introduce textlint to CI pipeline#4831
infra: Introduce textlint to CI pipeline#4831thompson-tomo wants to merge 10 commits intoopen-telemetry:mainfrom
Conversation
a700f5b to
f03393d
Compare
f03393d to
393d681
Compare
393d681 to
25511ae
Compare
|
This PR was marked stale. It will be closed in 14 days without additional activity. |
jsuereth
left a comment
There was a problem hiding this comment.
Overall - this looks great! Can you use it the same as other fix tools in the specification.
I added a few comments on "odd" renames I saw, in addition to agreeing with the ones called out.
What's your plan for these?
Yes, currently if you run
For the ones which we are in agreement on, they will be added to the config as allowed and I will ensure they are changed back. |
298e42b to
b4ea171
Compare
d819458 to
8240fec
Compare
fc9fb09 to
7cc59d6
Compare
|
@jsuereth i believe all open issues have been resolved with input from otel-comms on slack for the couple which we were not certain on. Could you take another look. |
Progresses #4728
Changes
This adds textlint into the CI pipeline to work alongside misspell/cspell.
TextLint will handle:
This is consistent with what OTEL.io does and addresses the ability to fix spelling issues via cli.
Note, the second commit is purely generated via the fix command for textlint and markdownlint. The textlint config file is take from otel.io.
For non-trivial changes, follow the change proposal process.
CHANGELOG.mdfile updated for non-trivial changes[chore]in the PR title to skip the changelog check