[CI][Doc] Add lint for markdown document

[hezean]

Purpose of the pull request

Resolves #8391

Ex. see https://github.com/HeZean/dolphinscheduler/actions/runs/2949741507

[hezean]

There are too many lint errors, I'll submit another PR to fix them

[codecov-commenter]

Codecov Report

Merging #11695 (17e0c43) into dev (145e441) will decrease coverage by 0.00%.
The diff coverage is n/a.

❗ Current head 17e0c43 differs from pull request most recent head 157d4e1. Consider uploading reports for the commit 157d4e1 to get more accurate results

@@             Coverage Diff              @@
##                dev   #11695      +/-   ##
============================================
- Coverage     39.81%   39.81%   -0.01%     
  Complexity     4718     4718              
============================================
  Files          1002     1002              
  Lines         37872    37872              
  Branches       4230     4230              
============================================
- Hits          15080    15077       -3     
- Misses        21191    21194       +3     
  Partials       1601     1601              

Impacted Files	Coverage Δ
...erver/master/processor/queue/TaskEventService.java	75.00% <0.00%> (-5.36%)	⬇️

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[EricGao888]

Sorry, I closed it by mistake just now. I've reopened it. This one is great, it could save our time for reviewing and fixing docs manually.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[hezean]

@EricGao888 can we merge this PR first, and fix the lint errors in another PR? I think that may make review easier

[EricGao888]

@EricGao888 can we merge this PR first, and fix the lint errors in another PR? I think that may make review easier

I'm fine with it. WDYT? @SbloodyS BTW, @hezean could you please add the key word related: #xxxxxxxx in another PR so that we could understand what another PR you are referring to.

[EricGao888]

LGTM, but I'm wondering whether there are any conflicts between spotless flexmark step and lint for markdown files? Have you experimented on it? @hezean

[kezhenxu94]

LGTM, but I'm wondering whether there are any conflicts between spotless flexmark step and lint for markdown files? Have you experimented on it? @hezean

I prefer we use a single linter (spotless) to do the linting stuffs. It's easier for developers to verify locally and don't require another learning how superlinter works

[hezean]

Thanks for the suggestion! I totally agree on it and will take a look at spotless, whereas I'm busy preparing for an important exam recently, please give me some time before I can step back to this pr.

[EricGao888]

LGTM, but I'm wondering whether there are any conflicts between spotless flexmark step and lint for markdown files? Have you experimented on it? @hezean

I prefer we use a single linter (spotless) to do the linting stuffs. It's easier for developers to verify locally and don't require another learning how superlinter works

+1

[EricGao888]

Thanks for the suggestion! I totally agree on it and will take a look at spotless, whereas I'm busy preparing for an important exam recently, please give me some time before I can step back to this pr.

@hezean Good luck with the exam : )

[kezhenxu94]

Is this fixed by #12006?

[hezean]

closing this outdated pr as finished in #12977