feat(rename-repo): Rename repository to graphql-protect #43
Conversation
This file contains 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
ldebruijn
added a commit
that referenced
this pull request
Jan 23, 2024
Rename the repository from go-graphql-armor to graphql-protect. Main reason for renaming are: - We have a lot of similarity with graphql-armor, which has a different purpose and feature set - Having `go-` in the name might confuse potential users about the purpose of graphql-protect, thinking it only applies for golang applications - graphql-shield was another option for the name, but is already taken by another solution. - graphql-protect also nicely conveys our purpose, and does not contend with similarly named solutions. After merging the repository URL will also be updated. Co-authored-by: ldebruijn <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Rename the repository from go-graphql-armor to graphql-protect.
Main reason for renaming are:
go-in the name might confuse potential users about the purpose of graphql-protect, thinking it only applies for golang applicationsAfter merging the repository URL will also be updated.