chore(git-blame): add formatting commits to ignore revs

[FucciUnavailable]

Description

Adding git ignore revs file so we can cleanup the noise from git blame for purely formatting commits

Fixes #690

Type of change

• Bug fix
• New feature
• Documentation
• Maintenance / refactor

Testing

• Tested locally
• All existing tests pass
• Added tests for new functionality (if applicable)

[Copilot]

Pull request overview

Updates the repository’s third-party notice generation pipeline (metadata + generator + CI drift check) and introduces a git-blame ignore list for mechanical formatting commits.

Changes:

• Rename the generated notice artifact from NOTICE.md to NOTICE and update the generator, Makefile targets, and the notice drift CI workflow accordingly.
• Add a _third_party_submissions block to scripts/notice-metadata.yaml and render it into NOTICE.
• Add a new .git-blame-ignore-revs file listing formatting/refactor commits to ignore in git blame.

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
scripts/notice-metadata.yaml	Adds _third_party_submissions metadata used to render contributor attribution into the notice output.
scripts/generate-notice.py	Updates output path to NOTICE and adds rendering/loading logic for the third-party submissions block.
NOTICE	Regenerated output including the new third-party submissions section.
Makefile	Updates comment to reflect NOTICE (no extension) generation target.
CHANGELOG.md	Adds Unreleased entries describing the notice rename and new submissions section.
.github/workflows/notice-drift.yml	Updates workflow comments/UI strings to refer to NOTICE instead of NOTICE.md.
.git-blame-ignore-revs	New ignore-revs list to improve git blame signal around formatting-only commits.

[Copilot]

The changelog guidance for this repo calls for one entry per PR; these are two separate bullets that both end with (#1073). Please combine into a single concise bullet (or otherwise justify why these should remain split) so the Unreleased section stays scannable and conforms to the project changelog rules.

[Copilot]

The comment says the NOTICE file ends with ---\n\n, but after appending the third-party-submissions block the rendered file now ends with that block (no trailing ---). Please either update the comment to match the new output shape, or add a trailing separator after the third-party section so the file still ends with the same template terminator.

Suggested change

	# Trailing blank line between components (and after the last one)
	# to match the CELA template -- the file ends `---\n\n`.
	out.append("\n")
	if tps is not None and tps.contributors:
	out.append(render_third_party_submissions(tps))
	# Trailing blank line between components (and after the last one).
	# If a third-party submissions section is appended below, we still
	# preserve the template terminator so the final file ends `---\n\n`.
	out.append("\n")
	if tps is not None and tps.contributors:
	out.append(render_third_party_submissions(tps))
	out.append("---\n\n")

[FucciUnavailable]

microsoft-github-policy-service agree

[danielmeppiel]

Thanks for sending this @FucciUnavailable, but closing as not-needed.

The two SHAs in the proposed file (2340fc77, 962fffd3) are pre-Ruff Black formatting commits. APM has since migrated to Ruff (ruff check + ruff format -- see .apm/instructions/linting.instructions.md), so those legacy commits aren't representative of the current formatting baseline.

#690 asks for adopting Ruff, which is already done -- I'll close that too as completed by the migration.

If we ever do a one-shot ruff format mass-rewrite worth hiding from blame, we can add a .git-blame-ignore-revs then with the right SHA. For now this would just ship dead bytes.

[FucciUnavailable]

Makes sense! Thank you for reviewing!