Base: Add note about optipng to contributing guidelines

A trick I learned from @linusg which is very useful and needs to be a part of PRs where images are involved.
Author: https://github.com/djwisdom Commit: https://github.com/SerenityOS/serenity/commit/c0e3d453c0 Pull-request: https://github.com/SerenityOS/serenity/pull/13893 Reviewed-by: https://github.com/linusg
2022-05-03 06:20:44 +08:00 · 2022-05-03 06:20:44 +08:00 · c0e3d453c0 · 2024-07-17 11:19:19 +09:00
commit c0e3d453c0
parent ab49fcfb7c
1 changed files with 1 additions and 0 deletions
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@ -55,6 +55,7 @@ Nobody is perfect, and sometimes we mess things up. That said, here are some goo
 * Squash your commits when making revisions after a patch review.
 * Add your personal copyright line to files when making substantive changes. (Optional but encouraged!)
 * Check the spelling of your code, comments and commit messages.
+* If you have images that go along with your code, run `optipng -strip all` on them to optimize and strip away useless metadata - this can reduce file size from multiple kilobytes to a couple hundred bytes.

 **Don't:**