Skip to content

Conversation

ZevEisenberg
Copy link
Contributor

Fix broken link to Swift forums.

Motivation:

The old link was a 404.

Old link: https://forums.swift.org/c/related-projects/swift-testing
New link: https://forums.swift.org/c/development/swift-testing/103

Modifications:

I looked on the forum and tried to find the most canonical version of the link. When I remove the /103, it still loads with a 301 Moved Permanently. I'm not sure whether including the /103 in the URL or not is more future-proof, but at least this way we prevent a redirect.

Result:

The link works again.

Checklist:

  • Code and documentation should follow the style of the Style Guide.
  • If public symbols are renamed or modified, DocC references should be updated.

@grynspan grynspan added bug 🪲 Something isn't working documentation 📚 Improvements or additions to documentation labels Mar 7, 2025
@grynspan grynspan added this to the Swift 6.x milestone Mar 7, 2025
@grynspan
Copy link
Contributor

grynspan commented Mar 7, 2025

@shahmishal Is there any way to get redirects working in the forums?

@grynspan
Copy link
Contributor

grynspan commented Mar 7, 2025

Docs change only, can skip CI.

Copy link
Contributor

@stmontgomery stmontgomery left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you! You are correct: we should include the trailing 103 digits in the URL, that is what allows Discourse forum URLs to properly redirect if a category is moved, and the problem is we didn't include those digits originally or the link wouldn't have broken. Lesson learned!

@stmontgomery stmontgomery merged commit ad8a13f into swiftlang:main Mar 7, 2025
@ZevEisenberg ZevEisenberg deleted the patch-1 branch March 7, 2025 13:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🪲 Something isn't working documentation 📚 Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants