Closed SauravMaheshkar closed 2 months ago
Well, without surprise....this yielded many changes necessary.
I think we may want to use
- use-quiet-mode: 'yes'
Specify yes to only show errors in output.
How would you like to proceed with this:
A) incorporate all links fixes in this PR. (maybe even one squash'ed commit) B) Merge this PR, and make subsequent PRs fixing the links.
Something else?
I think we're going to want to go with A otherwise it's going to break other PRs and the main branch. We squash PRs as a single commit so no worries about making lots of small commits. I'll give you a hand as soon as I can
Well, that was cumbersome, but that should do it!
A very few things was so old that I removed it.
Most were tracked down.
A couple in the CMake API I hardcoded, since the relative ../api/
links are dead in Markdown anyways, since api/
is generated a docgen-time
We might take a little while to review everything. Will get back to you once we got back to it.
Well, that was cumbersome, but that should do it!
A very few things was so old that I removed it. Most were tracked down. A couple in the CMake API I hardcoded, since the relative
../api/
links are dead in Markdown anyways, sinceapi/
is generated a docgen-timeWe might take a little while to review everything. Will get back to you once we got back to it.
Thanks for all the help @thomas-bc
@SauravMaheshkar would you be able to make the changes that were requested by LeStarch's review, as well as resolving the merge conflict? All changes from devel
in docs/UsersGuide/dev/testAPI/user_guide.md
should be taken in
Change Description
This PR adds a workflow for checking broken links in Markdown files
Rationale
Fixes #1840