-
Notifications
You must be signed in to change notification settings - Fork 0
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
CI: Add HTML validation to super-linter workflow #303
base: main
Are you sure you want to change the base?
Conversation
Would you mind to rebase this to see if the superlinter is happy now? |
@neteler Done |
@neteler theres still some. The one where you changed There's two unexpected closing div. Sometimes it's that a bit above a closing tag is interweaved instead of nested. |
I am preparing a big PR with tons of HTML fixes. Coming soon. |
In order to obtain a good result when converting the HTML manual pages files to markdown, ideally clean HTML code is used. This PR fixes numerous broken HTML tags identified during a test run of [adding HTML validation with super-linter](echoix#303). For reference, see logs showing the errors at https://github.com/echoix/grass/actions/runs/12001379426/job/33451802353?pr=303#step:4:8310 Fixes: - incomplete tag pairs - tabs replaced with white space
In order to obtain a good result when converting the HTML manual pages files to markdown, ideally clean HTML code is used. This PR fixes numerous broken HTML tags identified during a test run of [adding HTML validation with super-linter](echoix#303). For reference, see logs showing the errors at https://github.com/echoix/grass/actions/runs/12001379426/job/33451802353?pr=303#step:4:8310 Fixes: - incomplete tag pairs - tabs replaced with white space - fix missing .html extension in URLs
Merged in |
In progress |
ok, i skipped a lot and it’s starting to be big. |
I will improve further selected HTML bugs but
|
BTW: I wonder if the super-linter might better look at the final manual pages (i.e., the files generated during the compilation)? |
In order to obtain a good result when converting the HTML manual pages files to markdown, ideally clean HTML code is used (continuation of OSGeo#4765). This PR fixes numerous broken HTML tags identified during a test run of [adding HTML validation with super-linter](echoix#303). For reference, see logs showing the errors at https://github.com/echoix/grass/actions/runs/12067630007/job/33651008404?pr=303 Fixes include: - complete selected ncomplete tag pairs (esp. `<li>`) - tabs replaced with white space - `<`, `>`, `&` replaced with their HTML representations
Super-linter probably not, as it works better with committed files. Maybe running the tools directly once compiled/generated? But it might only be useful to run linters on generated files when developing, not ongoing use. Unless there's a point/argument I don't consider. |
Next brushup (hope the last): OSGeo#4781 |
* manual: fix more broken HTML tags In order to obtain a good result when converting the HTML manual pages files to markdown, ideally clean HTML code is used (continuation of #4765). This PR fixes numerous broken HTML tags identified during a test run of [adding HTML validation with super-linter](echoix#303). For reference, see logs showing the errors at https://github.com/echoix/grass/actions/runs/12067630007/job/33651008404?pr=303 Fixes include: - complete selected ncomplete tag pairs (esp. `<li>`) - tabs replaced with white space - `<`, `>`, `&` replaced with their HTML representations * Apply suggestions from code review --------- Co-authored-by: Edouard Choinière <27212526+echoix@users.noreply.github.com>
Backport of #4765 In order to obtain a good result when converting the HTML manual pages files to markdown, ideally clean HTML code is used. This PR fixes numerous broken HTML tags identified during a test run of [adding HTML validation with super-linter](echoix#303). For reference, see logs showing the errors at https://github.com/echoix/grass/actions/runs/12001379426/job/33451802353?pr=303#step:4:8310 Fixes: - incomplete tag pairs - tabs replaced with white space - fix missing .html extension in URLs
* manual: fix more broken HTML tags In order to obtain a good result when converting the HTML manual pages files to markdown, ideally clean HTML code is used (continuation of #4765). This PR fixes numerous broken HTML tags identified during a test run of [adding HTML validation with super-linter](echoix#303). For reference, see logs showing the errors at https://github.com/echoix/grass/actions/runs/12067630007/job/33651008404?pr=303 Fixes include: - complete selected ncomplete tag pairs (esp. `<li>`) - tabs replaced with white space - `<`, `>`, `&` replaced with their HTML representations * Apply suggestions from code review --------- Co-authored-by: Edouard Choinière <27212526+echoix@users.noreply.github.com>
No description provided.