Bugfix - Periodic URL checker

[avahoffman]

Periodic URL checker was failing for a few reasons:

• It was running on base_ottr, not with ubuntu-latest, and therefore didn't have the docker command line tools.
• The new ottr-reports makes an artifact, which wasn't clearly available to the rest of the workflow

Solution:

I broke down the ottr-reports and issue creation into separate jobs. This is a little cleaner because if ottr-reports succeeds, then it doesn't proceed to the issue creation step, create a branch with the errors, etc.

Examples:

• Shows failing but completes and creates an issue because of bad links
• Issue created
• Passing because all links are OK

---

Related: ottrproject/ottrproject.github.io#5

Resolves #21

[github-actions]

OTTR Check Results

Summary

• Spelling check: ✅ PASSED (0 errors found, threshold: 0)
• URL check: ✅ PASSED (0 errors found, threshold: 0)

🎉 All checks passed!

Last Updated: 2025-06-12-20:12:53

[github-actions]

Re-rendered previews from the latest commit:

• 👀 Quick preview of course website here *
• 🔬 Comprehensive download of the course website here
• Download the .docx file

* note not all html features will be properly displayed in the "quick preview" but it will give you a rough idea.

Updated at 2025-06-12 with changes from the latest commit d148902

[avahoffman]

This was the file used to test my theory.

[kweav]

This is so cool -- thanks!! And the tests look great --

1. Any tests or specific proofreading I can help with?
2. Any corresponding documentation changes I should make over on ottrproject.org?

[kweav]

Do we want the issue template to assign someone to the broken URL issue so we see it faster? Or because courses using the template would inherit that, not so much? Is there a way to easily assign someone with the config file -- and have people update their config files to change it from us to them?

[carriewright11]

Do we want the issue template to assign someone to the broken URL issue so we see it faster? Or because courses using the template would inherit that, not so much? Is there a way to easily assign someone with the config file -- and have people update their config files to change it from us to them?

I think this could be cool to allow people to put someone, a default is a bit odd though - maybe possible to leave blank

I also noticed that it doesn't use the config limits for errors

[avahoffman]

Any corresponding documentation changes I should make over on ottrproject.org?

@kweav I think the functionality should be similar but we could always update screenshots if any. Perhaps make an issue in the website repo so we don't forget?

I also noticed that it doesn't use the config limits for errors

We can easily use the config file! Will do.

Do we want the issue template to assign someone to the broken URL issue so we see it faster?

Maybe? Could we make an issue for this as an "enhancement" follow up?

[cansavvy]

This looks reasonable to me!