[ImgBot] Optimize images

[imgbot]

Beep boop. Your images are optimized!

Your image file size has been reduced by 9% 🎉

Details

File	Before	After	Percent reduction
/images/uri_basic_ko.png	19.35kb	13.69kb	29.26%
/images/file_upload_basic_ko.png	19.35kb	13.69kb	29.26%
/images/direct_input_basic_ko.png	33.92kb	24.59kb	27.51%
/images/vcss-blue.gif	1.72kb	1.31kb	23.76%
/images/vcss.gif	1.51kb	1.21kb	20.23%
/images/direct_input_basic_fr.png	48.60kb	41.13kb	15.36%
/images/direct_input_basic_pl.png	47.85kb	40.62kb	15.10%
/images/direct_input_basic_ja.png	51.75kb	43.94kb	15.09%
/images/css_validation_service.png	7.72kb	6.57kb	14.91%
/images/direct_input_basic_de.png	45.52kb	38.81kb	14.75%
/images/direct_input_basic.png	45.33kb	38.75kb	14.52%
/images/direct_input_basic_nl.png	45.18kb	38.69kb	14.37%
/images/header.png	29.99kb	25.70kb	14.30%
/images/direct_input_basic_es.png	45.91kb	39.35kb	14.28%
/images/direct_input_basic_it.png	45.98kb	39.63kb	13.82%
/images/direct_input_basic_zh.png	50.63kb	43.68kb	13.73%
/images/logo1.jpg	16.25kb	14.43kb	11.18%
/images/woolly-icon.png	3.14kb	2.89kb	8.17%
/docs/CSS_Validator_Sequence_Diagram.svg	68.03kb	64.22kb	5.59%
/images/lg_gradient.gif	0.15kb	0.14kb	5.37%
/images/sm_gradient_active.gif	0.15kb	0.14kb	5.30%
/images/sm_gradient_hover.gif	0.15kb	0.14kb	5.30%
/images/file_upload_basic_ja.png	30.68kb	29.40kb	4.19%
/images/file_upload_basic_fr.png	28.21kb	27.38kb	2.92%
/docs/CSS_Validator_Sequence_Diagram.png	347.82kb	338.04kb	2.81%
/images/uri_basic_zh.png	30.80kb	30.06kb	2.39%
/images/uri_basic_ja.png	29.60kb	29.02kb	1.97%
/images/file_upload_basic_pl.png	27.58kb	27.05kb	1.92%
/images/file_upload_basic_zh.png	30.58kb	30.08kb	1.63%
/images/file_upload_basic_es.png	27.30kb	26.86kb	1.60%
/images/vcss-old.gif	2.11kb	2.09kb	1.02%
/images/file_upload_basic_de.png	25.89kb	25.79kb	0.40%
/images/file_upload_basic_nl.png	26.76kb	26.68kb	0.28%
/images/vh40.gif	0.88kb	0.88kb	0.22%
/images/uri_basic_fr.png	25.55kb	25.51kb	0.19%
/images/vcss-new.gif	2.01kb	2.01kb	0.15%
Total :	1,263.94kb	1,154.16kb	8.69%

---

Black Lives Matter | 💰 donate | 🎓 learn | ✍🏾 sign

📝 docs | repo | 🙋🏾 issues | 🏅 swag | 🏪 marketplace

[pull-request-quantifier-deprecated]

Pull Request Quantified (No Changes)

This PR has 0 quantified lines of changes. In general, a change size of 50 to 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : No Changes
Size       : +0 -0
Percentile : 0%

Total files changed: 0

Change summary by file extension:

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detetcted.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.