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 suggestions #1883

Merged
merged 1 commit into from
Jan 3, 2022

Conversation

pre-commit-ci[bot]
Copy link
Contributor

@pre-commit-ci pre-commit-ci bot commented Jan 3, 2022

updates:

🛠️ PR Summary

Made with ❤️ by Ultralytics Actions

🌟 Summary

Update to pre-commit hooks for improved code quality checks.

📊 Key Changes

  • Updated pre-commit/pre-commit-hooks from v4.0.1 to v4.1.0.
  • Updated asottile/pyupgrade from v2.23.1 to v2.31.0.
  • Updated PyCQA/isort from 5.9.3 to 5.10.1.
  • Updated PyCQA/flake8 from 3.9.2 to 4.0.1.

🎯 Purpose & Impact

  • Enhanced Code Quality: Ensures that the codebase adheres to the latest standards by using updated versions of code quality tools.
  • Up-to-Date Practices: Adopts recent improvements and features in the tools, possibly catching more issues automatically.
  • Developer Experience: Offers developers a smoother experience with the most current tools for code formatting and linting.
  • End-User Benefits: Indirectly benefits end-users by maintaining a cleaner, more stable, and consistently styled codebase.

updates:
- [github.com/pre-commit/pre-commit-hooks: v4.0.1 → v4.1.0](pre-commit/pre-commit-hooks@v4.0.1...v4.1.0)
- [github.com/asottile/pyupgrade: v2.23.1 → v2.31.0](asottile/pyupgrade@v2.23.1...v2.31.0)
- [github.com/PyCQA/isort: 5.9.3 → 5.10.1](PyCQA/isort@5.9.3...5.10.1)
- [github.com/PyCQA/flake8: 3.9.2 → 4.0.1](PyCQA/flake8@3.9.2...4.0.1)
Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👋 Hello @pre-commit-ci[bot], thank you for submitting a 🚀 PR! To allow your work to be integrated as seamlessly as possible, we advise you to:

  • ✅ Verify your PR is up-to-date with upstream/master. If your PR is behind upstream/master an automatic GitHub actions rebase may be attempted by including the /rebase command in a comment body, or by running the following code, replacing 'feature' with the name of your local branch:
git remote add upstream https://github.com/ultralytics/yolov3.git
git fetch upstream
git checkout feature  # <----- replace 'feature' with local branch name
git merge upstream/master
git push -u origin -f
  • ✅ Verify all Continuous Integration (CI) checks are passing.
  • ✅ Reduce changes to the absolute minimum required for your bug fix or feature addition. "It is not daily increase but daily decrease, hack away the unessential. The closer to the source, the less wastage there is." -Bruce Lee

@glenn-jocher glenn-jocher merged commit 0f80f2f into master Jan 3, 2022
@glenn-jocher glenn-jocher deleted the pre-commit-ci-update-config branch January 3, 2022 18:33
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.

1 participant