-
Notifications
You must be signed in to change notification settings - Fork 16.4k
Implement simpler and faster freeze check for translations #55154
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
Conversation
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.
Nice improvement. (selective checks, flag + label)
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.
I would expect the workflows files to be updated accordingly, am I missing something? (I guess I am, can't remember how that ui_english_translation_changed props is invoked)
bb1cd5d to
b25c05f
Compare
) This is follow-up after apache#55119 - implements the translation freeze quite a bit simpler and faster: * uses selective checks (fail fast) * does not check the dates (we will set the flag to False when freeze time passes * you can bypass the freeze with a label rather than having to commit exemption file
…he#55325) When we run with "translation-changing" commit in a canary run, we should not fail the build as the change has already been deliberately merged (likely with "allow translation changes" label). Follow-up after apache#55154
) This is follow-up after apache#55119 - implements the translation freeze quite a bit simpler and faster: * uses selective checks (fail fast) * does not check the dates (we will set the flag to False when freeze time passes * you can bypass the freeze with a label rather than having to commit exemption file
…he#55325) When we run with "translation-changing" commit in a canary run, we should not fail the build as the change has already been deliberately merged (likely with "allow translation changes" label). Follow-up after apache#55154
) This is follow-up after apache#55119 - implements the translation freeze quite a bit simpler and faster: * uses selective checks (fail fast) * does not check the dates (we will set the flag to False when freeze time passes * you can bypass the freeze with a label rather than having to commit exemption file
…he#55325) When we run with "translation-changing" commit in a canary run, we should not fail the build as the change has already been deliberately merged (likely with "allow translation changes" label). Follow-up after apache#55154
) This is follow-up after apache#55119 - implements the translation freeze quite a bit simpler and faster: * uses selective checks (fail fast) * does not check the dates (we will set the flag to False when freeze time passes * you can bypass the freeze with a label rather than having to commit exemption file
…he#55325) When we run with "translation-changing" commit in a canary run, we should not fail the build as the change has already been deliberately merged (likely with "allow translation changes" label). Follow-up after apache#55154
) This is follow-up after apache#55119 - implements the translation freeze quite a bit simpler and faster: * uses selective checks (fail fast) * does not check the dates (we will set the flag to False when freeze time passes * you can bypass the freeze with a label rather than having to commit exemption file
…he#55325) When we run with "translation-changing" commit in a canary run, we should not fail the build as the change has already been deliberately merged (likely with "allow translation changes" label). Follow-up after apache#55154
) This is follow-up after apache#55119 - implements the translation freeze quite a bit simpler and faster: * uses selective checks (fail fast) * does not check the dates (we will set the flag to False when freeze time passes * you can bypass the freeze with a label rather than having to commit exemption file
…he#55325) When we run with "translation-changing" commit in a canary run, we should not fail the build as the change has already been deliberately merged (likely with "allow translation changes" label). Follow-up after apache#55154
) This is follow-up after apache#55119 - implements the translation freeze quite a bit simpler and faster: * uses selective checks (fail fast) * does not check the dates (we will set the flag to False when freeze time passes * you can bypass the freeze with a label rather than having to commit exemption file
…he#55325) When we run with "translation-changing" commit in a canary run, we should not fail the build as the change has already been deliberately merged (likely with "allow translation changes" label). Follow-up after apache#55154
) This is follow-up after apache#55119 - implements the translation freeze quite a bit simpler and faster: * uses selective checks (fail fast) * does not check the dates (we will set the flag to False when freeze time passes * you can bypass the freeze with a label rather than having to commit exemption file
…he#55325) When we run with "translation-changing" commit in a canary run, we should not fail the build as the change has already been deliberately merged (likely with "allow translation changes" label). Follow-up after apache#55154
) This is follow-up after apache#55119 - implements the translation freeze quite a bit simpler and faster: * uses selective checks (fail fast) * does not check the dates (we will set the flag to False when freeze time passes * you can bypass the freeze with a label rather than having to commit exemption file
…he#55325) When we run with "translation-changing" commit in a canary run, we should not fail the build as the change has already been deliberately merged (likely with "allow translation changes" label). Follow-up after apache#55154
) This is follow-up after apache#55119 - implements the translation freeze quite a bit simpler and faster: * uses selective checks (fail fast) * does not check the dates (we will set the flag to False when freeze time passes * you can bypass the freeze with a label rather than having to commit exemption file
…he#55325) When we run with "translation-changing" commit in a canary run, we should not fail the build as the change has already been deliberately merged (likely with "allow translation changes" label). Follow-up after apache#55154
) This is follow-up after apache#55119 - implements the translation freeze quite a bit simpler and faster: * uses selective checks (fail fast) * does not check the dates (we will set the flag to False when freeze time passes * you can bypass the freeze with a label rather than having to commit exemption file
…he#55325) When we run with "translation-changing" commit in a canary run, we should not fail the build as the change has already been deliberately merged (likely with "allow translation changes" label). Follow-up after apache#55154
) This is follow-up after apache#55119 - implements the translation freeze quite a bit simpler and faster: * uses selective checks (fail fast) * does not check the dates (we will set the flag to False when freeze time passes * you can bypass the freeze with a label rather than having to commit exemption file
…he#55325) When we run with "translation-changing" commit in a canary run, we should not fail the build as the change has already been deliberately merged (likely with "allow translation changes" label). Follow-up after apache#55154
) This is follow-up after apache#55119 - implements the translation freeze quite a bit simpler and faster: * uses selective checks (fail fast) * does not check the dates (we will set the flag to False when freeze time passes * you can bypass the freeze with a label rather than having to commit exemption file
…he#55325) When we run with "translation-changing" commit in a canary run, we should not fail the build as the change has already been deliberately merged (likely with "allow translation changes" label). Follow-up after apache#55154
) This is follow-up after apache#55119 - implements the translation freeze quite a bit simpler and faster: * uses selective checks (fail fast) * does not check the dates (we will set the flag to False when freeze time passes * you can bypass the freeze with a label rather than having to commit exemption file
…he#55325) When we run with "translation-changing" commit in a canary run, we should not fail the build as the change has already been deliberately merged (likely with "allow translation changes" label). Follow-up after apache#55154
) This is follow-up after apache#55119 - implements the translation freeze quite a bit simpler and faster: * uses selective checks (fail fast) * does not check the dates (we will set the flag to False when freeze time passes * you can bypass the freeze with a label rather than having to commit exemption file
…he#55325) When we run with "translation-changing" commit in a canary run, we should not fail the build as the change has already been deliberately merged (likely with "allow translation changes" label). Follow-up after apache#55154


This is follow-up after #55119 - implements the translation freeze quite a bit simpler and faster:
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.