You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Occasionally, broken links get introduced into the site, which we detect via a scheduled link check sometime they are included. It would be preferable to not introduce them at all.
To avoid this, we could check the files modified in pull request, in addition to having a regular scheduled link check.
If successful, we could also use this approach for other sites that we maintain.
Sometimes links aren't broken, but simply blocked because the site blocks the GitHub Actions runner and/or the Lychee client. The fix then is to add the link to the .lycheeignore, which is less obvious. Might this be extra confusion for pull request authors?
The text was updated successfully, but these errors were encountered:
Occasionally, broken links get introduced into the site, which we detect via a scheduled link check sometime they are included. It would be preferable to not introduce them at all.
To avoid this, we could check the files modified in pull request, in addition to having a regular scheduled link check.
If successful, we could also use this approach for other sites that we maintain.
Considerations:
.lycheeignore
, which is less obvious. Might this be extra confusion for pull request authors?The text was updated successfully, but these errors were encountered: