chore(deps): bump git2 from 0.14.4 to 0.16.1

[dependabot]

Bumps git2 from 0.14.4 to 0.16.1.

Commits

• a233483 Update to libgit2 1.5.1
• bce1555 Merge pull request #909 from ehuss/ssh-keys
• 222fbf3 Bump versions
• fa41943 Change the certificate_check callback to support passthrough.
• 84e21aa Add ability to get the SSH host key and its type.
• e6aa666 Bump git2-curl version. (#861)
• 46674ce Fix warning about unused_must_use for Box::from_raw (#860)
• 951dce9 Merge pull request #858 from davidkna/git2150
• 8871f8e bump libgit2 to 1.5.0
• 04278a2 Merge pull request #839 from davidkna/libgit2_143
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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 10 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +5 -5
Percentile : 4%

Total files changed: 2

Change summary by file extension:
.lock : +4 -4
.toml : +1 -1

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 detected.
• 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.

[codecov]

Codecov Report

Base: 51.81% // Head: 39.05% // Decreases project coverage by -12.77% ⚠️

Coverage data is based on head (477e98c) compared to base (2aaadf2).
Patch has no changes to coverable lines.

Additional details and impacted files

@@             Coverage Diff             @@
##           master     #155       +/-   ##
===========================================
- Coverage   51.81%   39.05%   -12.77%     
===========================================
  Files          10       10               
  Lines         577      443      -134     
===========================================
- Hits          299      173      -126     
+ Misses        278      270        -8     

Impacted Files	Coverage Δ
src/util.rs	66.66% <0.00%> (-13.71%)	⬇️
src/extensions.rs	79.41% <0.00%> (-8.31%)	⬇️
src/arguments.rs	81.53% <0.00%> (-5.06%)	⬇️
src/message.rs	13.04% <0.00%> (-4.99%)	⬇️
src/log.rs	100.00% <0.00%> (ø)
src/config.rs	77.77% <0.00%> (+3.30%)	⬆️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.