ferruzzi opened a new pull request, #68601: URL: https://github.com/apache/airflow/pull/68601
Part 7 of 6 :sweat_smile: , adding a few that I missed or don't fit neatly into one of the existing categories. Leaving this a a draft until I'm confident they are all covered. Follow-up to https://github.com/apache/airflow/pull/68108 Can be reviewed/merged in parallel with https://github.com/apache/airflow/pull/68367, https://github.com/apache/airflow/pull/68589, https://github.com/apache/airflow/pull/68593, https://github.com/apache/airflow/pull/68594, and https://github.com/apache/airflow/pull/68599 --- This should be the last one. For posterity: In order to check if I got them all, I made a list of the ones I have included in these 7 PRs then pointed Claude Opus 4.8 at the codebase with the following prompt: ``` Make a pass on all metrics in the entire codebase. For each metric, check if it could be tied to a team. Generate a report which contains three lists: 1) Metrics which can not be linked to a Team. 2) Metrics which can be linked to a Team and already include the team_name tag - count the metrics from the open PRs as done for the purpose of this list. 3) Metrics which can be linked to a Team and do not include the team_name tag. Finally, cross-check those lists to ensure that every metric you found exists on one and only one of those three lists. ``` and this was the generated report: <!-- SPDX-License-Identifier: Apache-2.0 https://www.apache.org/licenses/LICENSE-2.0 --> <!-- Thank you for contributing! Please provide above a brief description of the changes made in this pull request. Write a good git commit message following this guide: http://chris.beams.io/posts/git-commit/ Please make sure that your code changes are covered with tests. And in case of new features or big changes remember to adjust the documentation. For user-facing UI changes, please attach before/after screenshots (or a short screen recording) so reviewers can assess the visual impact. Feel free to ping (in general) for the review if you do not see reaction for a few days (72 Hours is the minimum reaction time you can expect from volunteers) - we sometimes miss notifications. In case of an existing issue, reference it using one of the following: * closes: #ISSUE * related: #ISSUE --> --- ##### Was generative AI tooling used to co-author this PR? <!-- If generative AI tooling has been used in the process of authoring this PR, please change below checkbox to `[X]` followed by the name of the tool, uncomment the "Generated-by". --> - [ ] Yes (please specify the tool below) <!-- Generated-by: [Tool Name] following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) --> --- * Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)** for more information. Note: commit author/co-author name and email in commits become permanently public when merged. * For fundamental code changes, an Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals)) is needed. * When adding dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). * For significant user-facing changes create newsfragment: `{pr_number}.significant.rst`, in [airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments). You can add this file in a follow-up commit after the PR is created so you know the PR number. -- 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]
