Add canonical NOTICE source and sync hook#67147
Closed
xchwan wants to merge 1 commit into
Closed
Conversation
Signed-off-by: Xch1 <qchwan@gmail.com>
Member
|
the notice file never changes - it can diverge. There is no point in syncing those, dfferent story with licence headers that are added to files and they are modified independently. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
issue: #60540
Summary
Introduces a canonical NOTICE template and a manual prek hook to keep all distribution NOTICE files in sync.
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.
Annual year updates are handled by a separate update-notice-year hook.
Was generative AI tooling used to co-author this PR?
Claude Code Sonnet 4.6
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.