Re: Possible conflicts after string normalization in providers

2022-11-10 Thread Daniel Standish
Ok -- just merged normalization for core. Now we're fully normalized. Expect conflicts in your branches (if they touch core airflow). Apologies in advance.

Re: Possible conflicts after string normalization in providers

2022-10-24 Thread Jarek Potiuk
Cool! :) On Mon, Oct 24, 2022 at 7:49 AM Daniel Standish wrote: > OK -- the non-providers/non-core (a.k.a. "other") group of string > normalization has just been merged. So, if you already rebased, unlucky > you -- you need to do it again. > > But fear not, you won't need to do it yet another

Re: Possible conflicts after string normalization in providers

2022-10-23 Thread Daniel Standish
OK -- the non-providers/non-core (a.k.a. "other") group of string normalization has just been merged. So, if you already rebased, unlucky you -- you need to do it again. But fear not, you won't need to do it yet another time until closer to the release of airflow 2.5, when we'll apply string

Re: Possible conflicts after string normalization in providers

2022-10-23 Thread Daniel Standish
Thanks Jarek There will be a couple more notices like this as we apply to the rest of the codebase. Non-providers / non-core is coming soon, and core will be applied closer to 2.5. And if you don't want to squash to one commit, I think you can also just do `pre-commit run black --all-files`,

Possible conflicts after string normalization in providers

2022-10-23 Thread Jarek Potiuk
Hey everyone, I have just merged the change from Daniel about string normalization in providers (https://github.com/apache/airflow/pull/27205). Anyone who had a PR for providers might (and likely will) have a conflict. It should be easy to fix though: 1. check that the only conflicting changes