Replace the dead GraphQL Armor forum link with the project documentation - #3467
Merged
Conversation
The Strapi Forum shut down and the topic returns 404 with no redirect, so the tip now points at GraphQL Armor's own getting-started documentation. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
added
pr: chore
source: CMS
internal
Collaborator
|
Good catch, thank you! 🫶 🚀 |
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
2 participants
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.
This PR replaces the dead GraphQL Armor link on the GraphQL plugin page. The Strapi Forum shut down and that topic returns 404 with no redirect, so the tip now points at GraphQL Armor's own getting-started documentation and describes what the tool is, rather than promising a Strapi-specific guide that no longer exists.