Skip to content
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

[pre-commit.ci] pre-commit autoupdate #761

Merged
merged 2 commits into from
Aug 31, 2024
Merged

Conversation

pre-commit-ci[bot]
Copy link
Contributor

@pre-commit-ci pre-commit-ci bot commented Aug 26, 2024

updates:
- [github.com/astral-sh/ruff-pre-commit: v0.6.1 → v0.6.2](astral-sh/ruff-pre-commit@v0.6.1...v0.6.2)
Copy link

codecov bot commented Aug 26, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.11%. Comparing base (16dcfc8) to head (adbe8a9).
Report is 4 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #761      +/-   ##
==========================================
- Coverage   74.13%   73.11%   -1.02%     
==========================================
  Files          30       30              
  Lines        1701     1696       -5     
==========================================
- Hits         1261     1240      -21     
- Misses        440      456      +16     

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

@dulmandakh dulmandakh merged commit 7c3bc21 into master Aug 31, 2024
63 checks passed
@dulmandakh dulmandakh deleted the pre-commit-ci-update-config branch August 31, 2024 08:40
@claudep
Copy link
Contributor

claudep commented Aug 31, 2024

@dulmandakh my practice is to only merge the pre-commit updates just before releasing a new version. I find that they mostly pollute the commit history with very little gain. It is personal taste, of course.

@dulmandakh
Copy link
Contributor

@dulmandakh my practice is to only merge the pre-commit updates just before releasing a new version. I find that they mostly pollute the commit history with very little gain. It is personal taste, of course.

Got it, I agree.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants