-
Notifications
You must be signed in to change notification settings - Fork 491
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
fix broken link #1000
fix broken link #1000
Conversation
these are honestly all over the place in my experience, any way we can lint these? |
i had some idea to list all links in the documents and all possible destinations and compare them (or something like this) |
this is about what i imagined, it does not work yet and has bugs |
I agree with the automatic check, but I disagree on the custom script, we should automate this process, and check with a Github action like this https://github.com/gaurav-nelson/github-action-markdown-link-check We should ran this action periodically, maybe 1 time each month? |
oh lol i did not search before making the script, but anyway it was fun to make
i would suggest with every pull request |
for sure, but also the url can be broken after X period of time, once the PR is landed (with valid URL) on the master |
ok yeah, a bit of an edge case, but good to also check those. i set it to every month and every pull request now |
are actions disabled in this repo? |
wow, there's a script for this already? :D glad I asked |
more people had issues with broken links before |
I think that the PR need to be merged before, otherwise creating a fake PR that trigger the CI can put down the Github action. I had an attack like these in one of my repo, while a go now github disable it |
ok i will merge it on my fork then to test it testing it here: antonilol#1 |
it did not catch the error... |
e0f6d5b
to
f4647f6
Compare
Does that mean the CI script you included doesn't work? Or am I misunderstanding? Not sure whether we should accept that change or just fix this specific broken link. |
Yes. It reported no errors where there was at least one. |
f4647f6
to
ff7457b
Compare
Let's try that in a separate PR to see if that works! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
again lol