Skip to content

Conversation

pre-commit-ci[bot]
Copy link
Contributor

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

updates:
- [github.com/asottile/pyupgrade: v3.16.0 → v3.17.0](asottile/pyupgrade@v3.16.0...v3.17.0)
- [github.com/adamchainz/django-upgrade: 1.19.0 → 1.20.0](adamchainz/django-upgrade@1.19.0...1.20.0)
- [github.com/astral-sh/ruff-pre-commit: v0.5.0 → v0.6.3](astral-sh/ruff-pre-commit@v0.5.0...v0.6.3)
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from 5b3a878 to fda0007 Compare September 2, 2024 19:44
@fsbraun fsbraun merged commit 4b4e778 into master Sep 2, 2024
18 of 20 checks passed
@fsbraun fsbraun deleted the pre-commit-ci-update-config branch September 2, 2024 19:51
@mrbazzan
Copy link
Contributor

I don't know how yet, but it seems this is the commit
that introduced the coverage error

@fsbraun
Copy link
Member

fsbraun commented Jan 16, 2025

@mrbazzan Oh, wow! It only affects the precommit ci, not the testing??

@mrbazzan
Copy link
Contributor

mrbazzan commented Jan 16, 2025 via email

@mrbazzan
Copy link
Contributor

I don't know how yet, but it seems this is the commit
that introduced the coverage error

Well, this commit didn't introduce the error. A change to actions/upload-artifact
happened at the same time

@fsbraun
Copy link
Member

fsbraun commented Jan 16, 2025

Yeah, thank makes sense!

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