Skip to content

Conversation

Jeymz
Copy link
Contributor

@Jeymz Jeymz commented Jul 31, 2024

Thank you for submitting a Pull Request (PR) to the Cheat Sheet Series.

🚩 If your PR is related to grammar/typo mistakes, please double-check the file for other mistakes in order to fix all the issues in the current cheat sheet.

Please make sure that for your contribution:

  • In case of a new Cheat Sheet, you have used the Cheat Sheet template.
  • All the markdown files do not raise any validation policy violation, see the policy.
  • All the markdown files follow these format rules.
  • All your assets are stored in the assets folder.
  • All the images used are in the PNG format.
  • Any references to websites have been formatted as [TEXT](URL)
  • You verified/tested the effectiveness of your contribution (e.g., the defensive code proposed is really an effective remediation? Please verify it works!).
  • [] The CI build of your PR pass, see the build status here.

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 😃

Jeymz and others added 2 commits July 19, 2024 23:45
- 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`.
@Jeymz Jeymz requested review from mackowski, jmanico and szh as code owners July 31, 2024 17:02
szh
szh previously approved these changes Jul 31, 2024
Copy link
Collaborator

@szh szh left a 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.

Copy link
Collaborator

@mackowski mackowski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that changes in the CODEOWNERS file will not work. GitHub also shows the notice about that in the PR
Screenshot 2024-08-01 at 09 06 21

@jmanico
Copy link
Member

jmanico commented Aug 3, 2024

Even though checks passed @mackowski still has concerns that seem very reasonable. What is next?

@szh
Copy link
Collaborator

szh commented Aug 5, 2024

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?

@szh
Copy link
Collaborator

szh commented Aug 5, 2024

Hmm, it seems I can do it from the web interface

@szh szh requested a review from mackowski August 7, 2024 16:02
@Jeymz
Copy link
Contributor Author

Jeymz commented Aug 7, 2024

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.

@szh szh merged commit 9d8e9e3 into OWASP:master Aug 7, 2024
3 checks passed
OngDevLab added a commit to OngDevLab/CheatSheetSeries that referenced this pull request Aug 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants