Skip to content

docs: fix broken Markdown link in built_in_math_bugs.md (bugzilla #717379) - #16441

Open
sarthakgupta1907-cell wants to merge 1 commit into
stdlib-js:developfrom
sarthakgupta1907-cell:fix/broken-link-bugzilla-717379
Open

sarthakgupta1907-cell wants to merge 1 commit into
stdlib-js:developfrom
sarthakgupta1907-cell:fix/broken-link-bugzilla-717379

Conversation

@sarthakgupta1907-cell

@sarthakgupta1907-cell sarthakgupta1907-cell commented Nov 1, 2026 •

Copy link
Copy Markdown

Progresses #9112.

Description

This pull request:

  • Fixes broken Markdown link in docs/misc/built_in_math_bugs.md by replacing the dead Bugzilla URL (show_bug.cgi?id=717379#c5) with an archived Wayback Machine URL.

Related Issues

Reference Packages

None, breaking new ground.

Questions

No.

Other

No.

Checklist

AI Assistance

  • Yes

  • Documentation (including examples)

Disclosure

I consulted AI to identify the correct archived URL replacement. The change was a one-line fix authored manually.

@sarthakgupta1907-cell
sarthakgupta1907-cell requested a review from a team November 1, 2026 16:24
@stdlib-bot stdlib-bot added First-time Contributor A pull request from a contributor who has never previously committed to the project repository. Needs Review A pull request which needs code review. labels Nov 1, 2026
@stdlib-bot

Copy link
Copy Markdown
Contributor

⚠️ Tracking Issue Closure Warning ⚠️

I noticed your PR description contains closing keywords ("Resolves", "Closes", or "Fixes") referencing a "Tracking Issue".

Why this matters:
Tracking issues should typically remain open until all related sub-issues are completed. GitHub automatically closes issues with such closing keywords when the PR is merged. For more information, see GitHub's documentation on using keywords in issues and pull requests.

Required action:
Use "Progresses" instead to reference the tracking issue without automatically closing it.

Thank you for your contribution to the project!

@stdlib-bot stdlib-bot added the Potential Duplicate There might be another pull request resolving the same issue. label Nov 2, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

First-time Contributor A pull request from a contributor who has never previously committed to the project repository. Needs Review A pull request which needs code review. Potential Duplicate There might be another pull request resolving the same issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants