-
Notifications
You must be signed in to change notification settings - Fork 16.4k
Get rid of the bleeding edge of our prek-hooks #60452
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
Get rid of the bleeding edge of our prek-hooks #60452
Conversation
gopidesupavan
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cool :)
jscheffl
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit and then LGTM!
Finally the Lucas-C pre-commit hook and octopin repo got released with changes we need so we can get rid of bleeding-edge.
20b4b6b to
5532e46
Compare
Backport failed to create: v3-1-test. View the failure log Run details
You can attempt to backport this manually by running: cherry_picker f94039b v3-1-testThis should apply the commit to the v3-1-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continue |
Finally the Lucas-C pre-commit hook and octopin repo got released with changes we need so we can get rid of bleeding-edge.
Finally the Lucas-C pre-commit hook and octopin repo got released with changes we need so we can get rid of bleeding-edge. (cherry picked from commit f94039b)
) Finally the Lucas-C pre-commit hook and octopin repo got released with changes we need so we can get rid of bleeding-edge. (cherry picked from commit f94039b) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
Finally the Lucas-C pre-commit hook and octopin repo got released with changes we need so we can get rid of bleeding-edge.
Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.