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 #246

Merged
merged 1 commit into from
Nov 6, 2024
Merged

Conversation

updates:
- [github.com/asottile/pyupgrade: v3.17.0 → v3.19.0](asottile/pyupgrade@v3.17.0...v3.19.0)
- [github.com/mgedmin/check-manifest: 0.49 → 0.50](mgedmin/check-manifest@0.49...0.50)
- [github.com/mgedmin/check-python-versions: 0.22.0 → 0.22.1](mgedmin/check-python-versions@0.22.0...0.22.1)
@mister-roboto
Copy link

@pre-commit-ci[bot] thanks for creating this Pull Request and helping to improve Plone!

TL;DR: Finish pushing changes, pass all other checks, then paste a comment:

@jenkins-plone-org please run jobs

To ensure that these changes do not break other parts of Plone, the Plone test suite matrix needs to pass, but it takes 30-60 min. Other CI checks are usually much faster and the Plone Jenkins resources are limited, so when done pushing changes and all other checks pass either start all Jenkins PR jobs yourself, or simply add the comment above in this PR to start all the jobs automatically.

Happy hacking!

@gforcada gforcada merged commit 43541f3 into main Nov 6, 2024
10 of 12 checks passed
@gforcada gforcada deleted the pre-commit-ci-update-config branch November 6, 2024 15:07
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