Bump github-pages from 212 to 227

[dependabot]

Bumps github-pages from 212 to 227.

Release notes

Sourced from github-pages's releases.

v227

Automated release for v227

v226

Automated release for v226

v225

Automated release for v225

What's Changed

• Pass the UNSAFE option to commonmark by @​yoannchaudet in github/pages-gem#821

Full Changelog: github/pages-gem@v224...v225

v224

Automated release for v224

What's Changed

• Update automation by @​felipesu19 in github/pages-gem#812
• Update tag/release script by @​felipesu19 in github/pages-gem#814
• Bump jekyll-commonmark-ghpages by @​yoannchaudet in github/pages-gem#820
• Bump jekyll-seo-tag to v2.8.0 by @​hubot in github/pages-gem#817

New Contributors

• @​felipesu19 made their first contribution in github/pages-gem#812

Full Changelog: github/pages-gem@v223...v224

v221

• Address CVE-2021-41098 #795

v220

• Bump pages-health-check to 1.17.9 github/pages-gem#790

v218

• Roll back remote themes for gem-based themes #781

v217

• #777 - Upgrade all pages-themes to v0.2.0 (except primer, which is v0.6.0)

NOTE: When building Jekyll locally using one of the Jekyll themes included in GitHub Pages, you will need to upgrade your _config.yml:

-theme: jekyll-theme-hacker
+remote_theme: pages-themes/hacker@v0.2.0
+plugins:
+  - jekyll-remote-theme

... (truncated)

Commits

• 26a8d15 Bump 💎 to v227
• f22e143 Merge pull request #842 from simonletort/master
• 3208cd4 nokogiri >=1.13.6
• fbcb667 Bump 💎 to v226
• eb24666 Merge pull request #826 from github/hubot/kramdown-v2-3-2
• 27126d8 Merge pull request #833 from github/jekyll-3.9.2
• 1809fd7 Merge pull request #831 from ohdle/patch-1
• e0c079b Bump jekyll to 3.9.2
• 65869db Require nokogiri 1.13.4 or greater
• e28d858 Update kramdown to 💎 v2.3.2
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[pull-request-quantifier-deprecated]

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

---

Quantification details

Label      : Medium
Size       : +96 -98
Percentile : 58.8%

Total files changed: 1

Change summary by file extension:
.lock : +96 -98

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.