Skip to content

chore: update py-gitguardian to 1.23.0 #1107

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jun 24, 2025

Conversation

gg-jonathangriffe
Copy link
Contributor

No description provided.

Copy link

codecov bot commented Jun 24, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.90%. Comparing base (e1f78c7) to head (1253100).
Report is 3 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1107   +/-   ##
=======================================
  Coverage   91.90%   91.90%           
=======================================
  Files         144      144           
  Lines        6102     6102           
=======================================
  Hits         5608     5608           
  Misses        494      494           
Flag Coverage Δ
unittests 91.90% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@gg-jonathangriffe gg-jonathangriffe force-pushed the jgriffe/update-py-gitguardian-to-1.23.0 branch from 400dfd2 to 1253100 Compare June 24, 2025 12:50
@gg-jonathangriffe gg-jonathangriffe merged commit 72e0ca2 into main Jun 24, 2025
29 checks passed
@gg-jonathangriffe gg-jonathangriffe deleted the jgriffe/update-py-gitguardian-to-1.23.0 branch June 24, 2025 13:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants