Skip to content

docs: describe the data-URL half of check:links in CONTRIBUTING - #1922

Merged
mrbobbytables merged 1 commit into
mainfrom
guide/docs-check-links
Oct 26, 2026
Merged

mrbobbytables merged 1 commit into
mainfrom
guide/docs-check-links

Conversation

@hivecommons-hive

Copy link
Copy Markdown
Contributor

Documentation Fix

Step 5 of CONTRIBUTING.md described check:links as "runs markdown-link-check over every *.md file in the repository". Since #1904, check:links is _check:links-md && _check:links-data: after the Markdown pass it also runs scripts/check-data-links.mjs over every outbound URL the site renders from data/. A contributor whose npm run check failed on a rotted data URL had no documented cause or remedy.

This PR updates the bullet to describe both halves and how to resolve a data-link failure: fix the URL in the data/ file, or add it to KNOWN_BROKEN_URLS in scripts/lib/data-links.mjs when the fix belongs upstream.

Verification: npx markdownlint --config .markdownlint.yaml CONTRIBUTING.md clean; node --test tests/contributing-just-build-parity.test.mjs tests/check-links-schedule-contract.test.mjs tests/check-aggregate-contract.test.mjs tests/workflow-scripts.test.mjs — 58/58 pass.

Claimed ground: CONTRIBUTING.md step 5, the check:links bullet only.

— hive: agent=guide backend=copilot model=kimi-k3 copilot=1.0.88

check:links has run scripts/check-data-links.mjs over the outbound URLs
the site renders from data/ since #1904, but step 5 still described it
as markdown-link-check only, leaving a contributor whose npm run check
fails on a rotted data URL with no documented cause or remedy.

Signed-off-by: guide <280983584+hivecommons-hive[bot]@users.noreply.github.com>
@hivecommons-hive

Copy link
Copy Markdown
Contributor Author

Important

Held for human review by the hive's ACMM level gate.

This PR was opened by the "guide" agent while Hive policy required a human checkpoint for that agent. Agent PRs are held at ACMM L3–L5; an outreach PR that targets a repository this hive does not manage is held at every level because it publishes project-facing communication into someone else's project.

Hive will keep the hold label until a human removes it. Operators can make a deliberate one-off release during an ACMM level change with release_level_holds=true, but level changes never release this hold automatically.

@netlify

netlify Bot commented Oct 25, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for endusers ready!

Name Link
🔨 Latest commit f91ce45
🔍 Latest deploy log https://app.netlify.com/projects/endusers/deploys/6ade96a06a4eac40362004c9
😎 Deploy Preview https://deploy-preview-1922--endusers.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@mrbobbytables
mrbobbytables added this pull request to the merge queue Oct 26, 2026
Merged via the queue into main with commit a398507 Oct 26, 2026
11 checks passed
@mrbobbytables
mrbobbytables deleted the guide/docs-check-links branch October 26, 2026 01:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant