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

Merged
merged 3 commits into from
Aug 21, 2023
Merged

Conversation

pre-commit-ci[bot]
Copy link
Contributor

@pre-commit-ci pre-commit-ci bot commented Aug 14, 2023

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

codecov bot commented Aug 14, 2023

Codecov Report

❗ No coverage uploaded for pull request base (main@b19a5ea). Click here to learn what that means.
The diff coverage is n/a.

❗ Current head 47c9b82 differs from pull request most recent head c26c82e. Consider uploading reports for the commit c26c82e to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1096   +/-   ##
=======================================
  Coverage        ?   82.69%           
=======================================
  Files           ?       35           
  Lines           ?     5090           
  Branches        ?        0           
=======================================
  Hits            ?     4209           
  Misses          ?      881           
  Partials        ?        0           

@flying-sheep flying-sheep added this to the 0.9.3 milestone Aug 17, 2023
@flying-sheep flying-sheep enabled auto-merge (squash) August 17, 2023 14:43
@flying-sheep flying-sheep merged commit 8341754 into main Aug 21, 2023
9 checks passed
@flying-sheep flying-sheep deleted the pre-commit-ci-update-config branch August 21, 2023 13:16
@lumberbot-app
Copy link

lumberbot-app bot commented Aug 21, 2023

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.9.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 8341754a1cc28c9e72f8788ffcf8cc29ba2adabb
  1. You will likely have some merge/cherry-pick conflict here, fix them and commit:
git commit -am 'Backport PR #1096: [pre-commit.ci] pre-commit autoupdate'
  1. Push to a named branch:
git push YOURFORK 0.9.x:auto-backport-of-pr-1096-on-0.9.x
  1. Create a PR against branch 0.9.x, I would have named this PR:

"Backport PR #1096 on branch 0.9.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