Migrate REST cheatsheet to WSTG #800
Merged
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
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
|
Various READMEs/ToCs should be updated to include the new doc. |
|
The content should be revised to follow the WSTG template and style guide |
|
@kingthorin this was just the move from the CSS project to here, I diverted the conversation back to the issue: #351 |
|
Instead of trying to place this when the conversation is still not done, I think I'll relocate it to root and just get this PR done. |
kingthorin
changed the title
GitHub issue: OWASP#351
kingthorin
force-pushed
the
issue-351-rest-assessment
branch
from
30bee82
to
826d0db
Compare
kingthorin
approved these changes
Apr 9, 2022
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.
GitHub issue: #351
This PR covers issue #351 .
What did this PR accomplish?
Thank you for your contribution!