Website Contains Broken Links about docs HOT 13 CLOSED

I thought about it as well but the one of the domains before is using 4 char domain name, and also some of them have trailing /. Will try it locally.

from docs.

https://twitter.com/nohwnd/status/1311575266813149186 ben taylor link
https://twitter.com/nohwnd/status/1311575722025250816 pwrshel link

from docs.

Glad to see you acting on this. There is still a link somewhere that is breaking the checker (as you can see at the bottom of the log). If you find out which one it is that would help a lot. Otherwise I will try to find it myself, somewhere next week.

from docs.

It seems to go line by line, so I guess it is the next one in that article.

  {
    title: "Visualizing Operational Tests with Jenkins and Pester",
    author: "Bill Hurt",
    date: "2016-06-25",
    url: "https://scripting.tech/2016/06/25/visualizing-operational-tests-with-jenkins-and-pester/",
  },

I don't see anything obviously bad about it, do you?

from docs.

Thanks for checking!

The only thing I can imagine is that the checker chokes on the 4-char domain name but who knows. It's possible to run the checker locally as well. Perhaps we can use that to eliminate/find the culprit.

npx broken-link-checker https://pester.dev --ordered --recursive

from docs.

stevenvachon/broken-link-checker#184 Blocked by this.

from docs.

Awesome find, I will see if I can resolve it using this info. A shame this guy seems to have abonded the tool, there were not many properly working alternatives (and I have checked a LOT).

from docs.

@nohwnd could you please trigger the github action, this "could" be resolved

from docs.

@bravo-kernel it still failed 6 days ago. So it is not resolved.

from docs.

You are correct. I am actually waiting on the v0.8.0-alpha release of the checker, then fix everything at once. Looks like he is alive and developing again. I would say... just a little more patience on this one.

On another topic, if you want, I can make some time to work with you on migrating the readme to the website. As long as the intended structure in known/in-place, the rest is just work. We can try solving the redirect issue as well then.

from docs.

If it is possible to grant me permissions to trigger the actions in this repo that would still be helpful.

from docs.

I was just looking at the pages and they seem to mostly be okay to merge now. The content seems to be a bit disjoint, but I would have to pour in at least two days to get it into the state I want, which I don't have at the moment. So I think we are okay to merge it.

from docs.

Closing in favor of #132.

• Github action now working as expected
• now using latest broken-link-checker

from docs.