24_proposing_best_practices_and_air_rules.rst

Proposing Airflow Best Practices and Ruff AIR Rules

This document explains how to propose a new Airflow best practice and, when appropriate, a matching Ruff AIR rule.

Not every best practice needs a linter rule, but for practices that can be checked automatically, AIR rules help contributors and users detect issues early and keep code consistent.

Proposal process

1. Begin the voting process or initiate a Lazy Consensus regarding migration, deprecation, or any other issue where there is strong community agreement. If someone opposes the decision, we can revisit the discussion and hold another vote.
2. Once the vote or Lazy Consensus is approved, create a pull request and update the Airflow best practices documentation. At this point, the development of Ruff rules can proceed concurrently.
3. After the pull request for Ruff is merged, ensure that the relevant documentation is updated to incorporate the new Ruff rules accordingly.

See also

• How to communicate
• ASF Voting Process