-
-
Notifications
You must be signed in to change notification settings - Fork 638
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
docs: added content for securing operations #1881
Conversation
Co-authored-by: Akshat Nema <[email protected]>
Co-authored-by: Akshat Nema <[email protected]>
Co-authored-by: Akshat Nema <[email protected]>
Co-authored-by: Akshat Nema <[email protected]>%0ACo-authored-by: Alejandra Quetzalli <[email protected]>%0ACo-authored-by: Lukasz Gornicki <[email protected]>
Co-authored-by: Lukasz Gornicki <[email protected]>
Co-authored-by: Lukasz Gornicki <[email protected]>
…ter-embed and eslint-plugin-react (#1832)
Co-authored-by: Lukasz Gornicki <[email protected]>
@BhaswatiRoy why there are references/changes to older commits in your PR? Have you rebased the PR? |
Kindly make sure, you make the PR, with your changes only. It's difficult for reviewers now to point out your changes. |
#1690) Co-authored-by: Akshat Nema <[email protected]>
@BhaswatiRoy @alequetzalli What's the status of this PR? Are you still working on this? |
hello, yes I was suggested by Rohit, to close this PR and reopen this by forking the next-major-specs branch |
@akshatnema Hey Akshat, the issue this PR resolves is part of the GSoD'23, @BhaswatiRoy will be working on resolving the issue and bringing the document in context to life😁. There were couple of things that needed to be fixed, so I suggested her to close this PR and open a new one with required changes and right base. :) You can find her new PR resolving the issue here. Thanks! |
Fix: #1513
Content:
Work: GSoD 2023 issue