-
Notifications
You must be signed in to change notification settings - Fork 8
Add GraphQL Security #387
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add GraphQL Security #387
Conversation
|
@-c3b5aw on 2022-07-25 08:50 says: unicorn |
|
@-sindresorhus on 2022-07-25 14:42 says: Thanks for making an Awesome list! 🙌 It looks like you didn't read the guidelines closely enough. I noticed multiple things that are not followed. Try going through the list point for point to ensure you follow it. I spent a lot of time creating the guidelines so I wouldn't have to comment on common mistakes, and rather spend my time improving Awesome. |
|
@-c3b5aw on 2022-07-26 15:36 says:
Hello @-sindresorhus, I reviewed the guidelines one more time and nothing related to the list itself is uncompliant. |
|
@-bytecauldron on 2022-07-30 21:47 says: Hi @-c3b5aw, Hope you are doing well. I noticed just a couple formatting-related issues but nothing too crazy.
Hope that helps. 😎 |
|
@-c3b5aw on 2022-07-30 22:37 says:
Thanks for catching theses point. Will improve right away. |
|
@-c3b5aw on 2022-07-30 22:51 says: Hello @-sindresorhus, This is ready for review. |
|
@-c3b5aw on 2022-09-11 10:15 says:
You are reviewing a closed PR though. |
|
@-alex-semenyuk on 2022-09-11 10:52 says: Sorry @-c3b5aw Are you going to reopen it or it's closed forever? I saw this
and think that it's ready for review again |
Pull request from @c3b5aw.
awesome-graphql-security
GraphQL Security is a niche ecosystem which get more and more attention as GraphQL grow.
We decided to create an awesome list to push this ecosystem ahead and we already reached a lot of people (55+ stars, 6 contributors, following guildelines and automated workflows...).
[ boilerplate snipped ]