[v3-0-test] Do not modify openapi-gen generated files by pre-commits … #51757
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
potiuk
requested review from
ashb,
bbovenzi,
gopidesupavan,
jscheffl,
pierrejeambrun,
ryanahamilton and
vincbeck
as code owners
boring-cyborg
bot
added
area:API
jscheffl
approved these changes
Jun 15, 2025
…pache#51755) The openeop-gen files do not follow our formatting and whitespace expectations - which means that our linting rules and whitespace pre-commit might complain and mofify them after they are generated. But we definitely do not want it and, hey - they are generated so we should just skip them whenever we do linting or whitespace correction. (cherry picked from commit 2c92125) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
potiuk
force-pushed
the
backport-2c92125-v3-0-test
branch
from
deea9ba to
9ffb1c0
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…(#51755)
The openeop-gen files do not follow our formatting and whitespace expectations - which means that our linting rules and whitespace pre-commit might complain and mofify them after they are generated.
But we definitely do not want it and, hey - they are generated so we should just skip them whenever we do linting or whitespace correction. (cherry picked from commit 2c92125)
^ 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.