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

Merged
merged 1 commit into from
Nov 14, 2023

Conversation

pre-commit-ci[bot]
Copy link
Contributor

@pre-commit-ci pre-commit-ci bot commented Nov 13, 2023

updates:
- [github.com/astral-sh/ruff-pre-commit: v0.1.4 → v0.1.5](astral-sh/ruff-pre-commit@v0.1.4...v0.1.5)
@flying-sheep flying-sheep added this to the 1.9.7 milestone Nov 14, 2023
@flying-sheep flying-sheep enabled auto-merge (squash) November 14, 2023 10:14
@flying-sheep flying-sheep merged commit 05dcf68 into master Nov 14, 2023
10 of 12 checks passed
@flying-sheep flying-sheep deleted the pre-commit-ci-update-config branch November 14, 2023 10:31
Copy link

lumberbot-app bot commented Nov 14, 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 1.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 05dcf68f32ce255447ea804de55babefb3c47c92
  1. You will likely have some merge/cherry-pick conflict here, fix them and commit:
git commit -am 'Backport PR #2753: [pre-commit.ci] pre-commit autoupdate'
  1. Push to a named branch:
git push YOURFORK 1.9.x:auto-backport-of-pr-2753-on-1.9.x
  1. Create a PR against branch 1.9.x, I would have named this PR:

"Backport PR #2753 on branch 1.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
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant