Confirm scheduled broken-link-detection automation - #211
Merged
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
digitaldiina
force-pushed
the
81-scheduled-broken-links
branch
from
August 11, 2026 06:29
86ca792 to
8a45859
Compare
mint automations create --type broken-link-detection --cron "0 6 1,15 * *" is now active (created 2026-08-11, first run 2026-08-15), no automerge. Fills in the placeholder left in contribute/automated-tests.mdx by #137's PR with the confirmed mint automations list output.
digitaldiina
force-pushed
the
81-scheduled-broken-links
branch
from
August 11, 2026 06:44
8a45859 to
3f5a963
Compare
Prose dates use "Month D, YYYY" elsewhere in this repo, not ISO - fixed. Also cut the "created now vs. waiting for launch" credit rationale - PR history already covers that reasoning, doesn't need to live in the durable reference page too.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #81.
Stacked on #207 (not yet merged) - this branch was cut from
137-ci-workflowssincecontribute/automated-tests.mdx(added there) is where this issue's findings live. The diff below will narrow to just this PR's own commit once #207 merges.Investigated the issue's own "native alternative" question
#81 explicitly asks to check whether Mintlify offers a native broken-link monitoring feature before building a custom scheduled job. It does:
mint automations create --type broken-link-detection --cron "<expr>"- a hosted automation that periodically re-scans the whole site and can auto-fix broken links (rename/move detection, or copy edits when a target was removed) by opening a PR.What was created
contribute/automated-tests.mdxfor the reasoning).tools/triage-broken-links.py+mint broken-linksCLI stay documented as the manual/second-opinion method, given a Mintlify community report of the hosted check under-reporting in some cases (HTTP 200 served for an actual 404).What shipped
contribute/automated-tests.mdx's "Scheduled check" section, filled in with the confirmedmint automations listoutput (status: active,nextRunAt: 2026-08-15T06:00:00.000Z).Verification
mint automations createoutput and a follow-upmint automations listboth confirmedstatus: active, correct cron/type, noautomergefield.markdownlint-cli2 contribute/automated-tests.mdx: 0 issues.