potiuk commented on PR #55416: URL: https://github.com/apache/airflow/pull/55416#issuecomment-3399347746
> The currect check strategy implies that if I fix an AirflowException-typo that I am not allowed to.I asusme this is for the moment acceptable... just am thinking about this. But have no other good strategy idea in mind. Maybe better solution: * dump (automatically) list of used Exceptions to a .txt file * fail if a found exception is not on the list * add a flag to the script to clean-up removed exceptions when `--all-files` are used * `prek run check_no_new_airflow_exceptions_added` (default - fails if not on list) * `prek run check_no_new_airflow_exceptions_added --all-files` (check all) * `scripts/ci/prek/check_no_new_airflow_exceptions_added.py --cleanup` - removes all exceptions from .txt file when already removed in the code Or similar. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
