-
Notifications
You must be signed in to change notification settings - Fork 4.2k
General Markdown Maintenance & Addition of Dockerfile for Easy Testing w/o Python #1459
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
Conversation
- Added `Dockerfile` for containerized local testing. - Updated lint task to cover all markdown files except `node_modules` and `cheatsheets_excluded`. - Resolved markdown lint issues identified in various repository files. - Added additional suggestion for `File_Upload_Cheat_Sheet.md`.
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.
I'm super excited about this. Should make things smoother for the upcoming bug bash (#1451). Docker workflow works great.
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.
Even though checks passed @mackowski still has concerns that seem very reasonable. What is next? |
I tried to push a commit that removes the section of the CODEOWNERS file with the error, but I'm getting "permission denied" despite the "Maintainers are allowed to edit this pull request" setting. @Jeymz can you take care of it instead? |
Hmm, it seems I can do it from the web interface |
Sorry for the lack of response. I don't regularly check github since it's not my primary working repository. It looks like Shlomo was able to resolve the issues. This was not an issue with the update but was an issue with an outdated entry that was still included in the codeowners I believe. Should probably warrant a regular review of those permissions. |
…y Testing w/o Python (OWASP#1459)" This reverts commit 9d8e9e3.
Thank you for submitting a Pull Request (PR) to the Cheat Sheet Series.
Please make sure that for your contribution:
[TEXT](URL)
If your PR is related to an issue, please finish your PR text with the following line:
This PR covers issue N/A.
Thank you again for your contribution 😃