-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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 documentation for why we need CSRF protection and how the protection works. #13430
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/hold
How are people supposed to find this? I suspect no one will ever read it.
Can we link to it from deck's main readme, or more likely the place in deck's code where we require (when I'm reading that code is the most likely time I'll be interested in getting more info).
LGTM label has been added. Git tree hash: 866843ba40aeb384fa3e5063b019e23afa1772c5
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fejta, mirandachrist The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this in a separate PR to the actual implementation of CSRF protection?
Adds documentation for why we need CSRF protection and how the protection works.
New changes are detected. LGTM label has been removed. |
My pixelbook and I were not getting along. Should I add it to the other PR? |
There isn't a deck readme as far as I can tell. I linked it in main.go in my other PR |
Adding this to the PR that adds CSRF protection SGTM |
As requested in #13323
/assign @fejta
/cc @cjwagner @Katharine