xchwan opened a new pull request, #67147:
URL: https://github.com/apache/airflow/pull/67147

    <!-- 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.
   
   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: #60540
   -->
   Summary
   
   Introduces a canonical NOTICE template and a manual prek hook to keep all 
distribution NOTICE files in sync.
   
   Problem
   
   The repo has 170+ NOTICE files maintained independently. When the ASF header 
needs updating (e.g. wording change, year), every file must be touched manually 
with no automation to ensure consistency.
   
   Changes
   
   New scripts/ci/license-templates/NOTICE — canonical ASF header for all 
standard distributions. This is the single source of truth; all standard 
provider/SDK NOTICE files should match it exactly.
   New scripts/ci/prek/sync_notice_files.py — manual-stage prek hook that:
   Overwrites standard NOTICE files that diverge from the canonical source
   For NOTICE files containing a 
======================================================================= 
separator (vendored-in third-party content: airflow-core, chart, 
providers/fab), only updates the copyright year and leaves the custom sections 
untouched
   Automatically excludes node_modules, .git, .venv, .build
   No hardcoded distribution list — presence of the separator is sufficient to 
detect custom content
   Updated .pre-commit-config.yaml — registers sync-notice-files as a manual 
hook
   Updated airflow-core/NOTICE, chart/NOTICE, providers/fab/NOTICE — restored 
original line break and separator format 
(=======================================================================, 71 
chars) which had drifted
   Usage
   
   Run once whenever the canonical source changes:
   ```
   prek run sync-notice-files --all-files
   ```
   Out of scope
   
   Annual year updates are handled by a separate update-notice-year hook.
   ---
   
   ##### 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".
   -->
   
   - [X] Yes (please specify the tool below)
   Claude Code Sonnet 4.6
   <!--
   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]

Reply via email to