Automated URL check findings (2026-03-01)

[nonprofittechy]

Automated URL check run on 2026-03-01 found link issues in docassemble-ALKilnSetup.

URLs returning HTTP 404/410

• [My response: Link made with code. Original:] [404] https://github.com/$ (found in: docassemble/ALKilnSetup/data/questions/al_set_up_testing.yml)
• [My response: Example link, Original:] [404] https://github.com/TheLawFantastic/docassemble-GreatForm** (found in: docassemble/ALKilnSetup/data/questions/al_set_up_testing.yml)
• [My response: Example link. Original:] [404] https://github.com/owner_name/repo_name** (found in: docassemble/ALKilnSetup/data/questions/al_set_up_testing.yml)
• [My response: Non-exsistent. Original:] [404] https://techbrightsystems.com/incognito-mode/ (found in: docassemble/ALKilnSetup/data/questions/al_set_up_testing.yml)

URLs unreachable at check time

• [**My response: Example link] https://legal-dev.org (found in: docassemble/ALKilnSetup/data/questions/al_set_up_testing.yml)

This issue was opened automatically from a cross-repository URL integrity check.

[plocket]

None of these links needed fixing.

[nonprofittechy]

@plocket these will continue to flag as errors until you whitelist them, or change to a url with a TLD of "example".

Edit: this is also currently a 404: https://techbrightsystems.com/incognito-mode/

[plocket]

Edit: this is also currently a 404: https://techbrightsystems.com/incognito-mode/

Where are you finding this link, though? I haven't found it.

these will continue to flag as errors until you whitelist them, or change to a url with a TLD of "example".

So ["example.com"] (see validation code here) "foo.example", thanks for the tip. If you haven't already done it, in a future version, the action that creates these issues it would be useful to include that tip. [Along with instructions on how to whitelist the links].

[plocket]

[Whitelisted now]

@nonprofittechy btw, I can't change https://github.com/$. It's creating a custom link dynamically.

[How do I whitelist the links?]

[plocket]

This should be solved.

[Se instructions below] For People of the Future, I found the code for the link-checker whitelisting here: https://github.com/SuffolkLITLab/DAYamlChecker/blob/c6a102f7aa6e1be8cef7e2688420d8f144695fd2/src/dayamlchecker/check_questions_urls.py#L300

[plocket]

@nonprofittechy

techbrightsystems.com

A search surfaces this link in a fork of this repo: https://github.com/Daenecompass/docassemble-ALAutomatedTestingTests/blob/f2aa2ab12af5583e0b63b3cc87122452a50638ed/docassemble/ALAutomatedTestingTests/data/questions/al_set_up_testing.yml#L371

The source original source may be https://github.com/swrdfgd/RandomWebsite/blob/87e635d02ba9fe700ddf3591c85bef358067af37/site1861.js#L250

Does this tool handle forks appropriately?

[nonprofittechy]

This should be solved.

For People of the Future, I found the code for the link-checker whitelisting here: https://github.com/SuffolkLITLab/DAYamlChecker/blob/c6a102f7aa6e1be8cef7e2688420d8f144695fd2/src/dayamlchecker/check_questions_urls.py#L300

This should be an easier reference: https://github.com/SuffolkLITLab/DAYamlChecker/blob/c6a102f7aa6e1be8cef7e2688420d8f144695fd2/README.md#url-checks

Or https://github.com/SuffolkLITLab/ALActions/#usage-7 for specifically taking care of in CI.

To clarify, this issue was generated by a one-time check. The place to whitelist is in the github action so automated CI passes.

And agreed, we should add a documentation page about how to configure da_build action and the different parameters you have now to tune and whitelist the increasingly robust automated checks.

[BryceStevenWilley]

techbrightsystems.com

This was present in this repo and was fixed in 660df75 on March 3rd, a few days after Quinten made the issue.

[plocket]

Will be closed by #247 when ready.