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

Merged
merged 1 commit into from
Dec 10, 2024
Merged

Conversation

pre-commit-ci[bot]
Copy link
Contributor

@pre-commit-ci pre-commit-ci bot commented Dec 9, 2024

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

codecov bot commented Dec 9, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 84.55%. Comparing base (018a041) to head (bdc2eb4).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1798      +/-   ##
==========================================
- Coverage   87.03%   84.55%   -2.49%     
==========================================
  Files          40       40              
  Lines        6085     6085              
==========================================
- Hits         5296     5145     -151     
- Misses        789      940     +151     

see 8 files with indirect coverage changes

@flying-sheep flying-sheep added this to the 0.11.2 milestone Dec 10, 2024
@flying-sheep flying-sheep enabled auto-merge (squash) December 10, 2024 08:56
@flying-sheep flying-sheep merged commit f1f6bf4 into main Dec 10, 2024
18 of 22 checks passed
@flying-sheep flying-sheep deleted the pre-commit-ci-update-config branch December 10, 2024 08:56
Copy link

lumberbot-app bot commented Dec 10, 2024

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

  1. Checkout backport branch and update it.
git checkout 0.11.x
git pull
  1. Cherry pick the first parent branch of the this PR on top of the older branch:
git cherry-pick -x -m1 f1f6bf41bffe6a8caca0b3956251440ec5548309
  1. You will likely have some merge/cherry-pick conflict here, fix them and commit:
git commit -am 'Backport PR #1798: [pre-commit.ci] pre-commit autoupdate'
  1. Push to a named branch:
git push YOURFORK 0.11.x:auto-backport-of-pr-1798-on-0.11.x
  1. Create a PR against branch 0.11.x, I would have named this PR:

"Backport PR #1798 on branch 0.11.x ([pre-commit.ci] pre-commit autoupdate)"

And apply the correct labels and milestones.

Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!

Remember to remove the Still Needs Manual Backport label once the PR gets merged.

If these instructions are inaccurate, feel free to suggest an improvement.

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.

1 participant