chore: rewrite v2 component history to preserve git blame

[balzss]

Summary

Rewrites master's history so that git blame on v2/* component files traces back through their v1/* predecessors (and through them, to the pre-multi-version originals). Today, 211 of 479 v2 files have squashed blame because the commits that introduced them used git add rather than git mv.

The working tree at the tip of this branch is byte-identical to master — only the commit history leading up to it differs. Verified by tree-hash comparison: 1f10331faa2931ac26fc7f24dfec8cbe67bb6489 on both sides.

What changed

For each of 18 "split" commits that introduced v2 files (full list below), a synthetic predecessor commit was inserted that does a pure git mv v1/X → v2/X. The original commit's tree is unchanged. The synthetic-rename gives git's rename detection something to lock onto when running blame on v2 files; the next commit recreates v1, so v1 files lose their post-split blame but their full prior history is intact up to that point.

This is the technique from the original #2486 PR, re-applied to current master (since master has moved 160 commits and added new v2 components since #2486 was opened in March).

Split commits rewritten

Files	Commit	Description
301	f691f0b96e	refactor(many): add multi-version support for finished packages
137	8e0f9ef7e6	refactor(many): add pr components to the refactor
37	fd7780fc7b	feat(ui-color-picker): rework ColorPicker
26	4f49e3e27d	feat(ui-buttons): add v2 button components
21	fb95519583	feat(many): rework Select/SimpleSelect/TimeSelect
17	0562fe2b43	feat: rework Drilldown
9	fba6b4d6a7	feat: rework AppNav
9	af97f0c0bc	feat: rework Rating
9	a99d7fe70b	refactor(many): fix migration bugs
8	36c02c6b3e	feat: rework DataPermissionLevels and NutritionFacts
6	335cc5b00b	feat: rework Mask
5	a201f69884	feat: rework ToggleDetails
5	5e7a355640	feat: rework Img
5	10f637b938	feat: rework InPlaceEdit and Editable
5	066524ff00	feat: rework Byline
4	ff5f2b3866	fix(ui-many): fix imports of the multiversion support
3	5a9405c0a1	feat: rework DateTimeInput/replace DateInput v1
1	30035d3544	chore(ui-scripts): combined svc-instui token changes

608 v1→v2 file pairs processed across the 18 commits.

Verification

Check	Result
git diff rewrite-v2-blame origin/master	empty (0 files)
Tree hashes match	1f10331faa… on both sides
pnpm run test:vitest	186 files, 2,181 tests pass (3 files / 46 tests skipped, same as master)
Total unique blame commits across 479 v2 files	3,661 → 5,684 (+55%)
Files with improved blame	211
Files unchanged	261 (already had good blame from earlier git mvs)
Files with reduced commit count	7 (each one is a more accurate attribution — formerly misattributed to random files via similar boilerplate, now traces to the true ancestor)

Sample improvements (before → after unique blame commits)

File	master	this branch
ui-buttons/Button/v2/index.tsx	2	27
ui-alerts/Alert/v2/index.tsx	2	33
ui-modal/Modal/v2/index.tsx	4	28
ui-img/Img/v2/index.tsx	2	23
ui-pagination/Pagination/v2/index.tsx	3	46
ui-select/Select/v2/index.tsx	3	55
ui-checkbox/Checkbox/v2/index.tsx	6	34

Earliest blame reached on Button/v2/index.tsx: ed73df19f78 (serikjensen, Dec 2019, packages/ui-buttons/Button/index.js).

Tradeoffs

• v1 files lose their post-split blame. Each v1 file's git history starts fresh at its corresponding split commit (its pre-split blame is preserved). Since v1 is legacy (cf. feat(many): remove deprecated v2 items #2549), this seems acceptable.
• All SHAs from 15f3c41cc7 (merge-base) onward change. Tags v11.7.0–v11.7.3 continue to point at their original (now orphaned) SHAs unless re-tagged. npm artifacts are unaffected.
• Open PRs need rebase. feat(many): remove deprecated v2 items #2549, Rework documentation #2550, refactor(many): extract raw svgs for cross-package use #2543, fix(ui-form-field): disable child inputs when FormFieldGroup is disabled #2542, chore(ui-utils): remove unused hash utility #2540, Calendar accessibility fix #2529, fix(ui-date-input): add scrollbar to dateinput v2 #2520, fix(ui-motion): use elementRef instead of ref in BaseTransition renderChildren #2514, wip: mobile topnav poc #1644 — each just needs git fetch && git rebase origin/master after the force-push.

Replaces #2486

The two non-history pieces of #2486 — test migration and the create-component-version script — have already landed independently on master. #2486 will be closed in favor of this PR once review begins.

Deployment

After review/approval:

1. Announce merge freeze on master.
2. Push rewrite-v2-blame to master with git push --force-with-lease origin rewrite-v2-blame:master.
3. Each contributor: git fetch && git reset --hard origin/master on local master, then rebase any in-progress branches.
4. (Optional) Re-tag v11.7.0–v11.7.3 against rewritten SHAs if you want tags to live in the new history.

Test plan

• git diff rewrite-v2-blame origin/master produces no output
• git rev-parse rewrite-v2-blame^{tree} matches git rev-parse origin/master^{tree}
• pnpm run bootstrap && pnpm run test:vitest passes
• git blame packages/ui-buttons/src/Button/v2/index.tsx shows ≥20 unique commits and traces back to 2019 ui-buttons/Button/index.js
• git blame packages/ui-modal/src/Modal/v2/index.tsx shows ≥20 unique commits and traces back to the original Modal/index.js

🤖 Generated with Claude Code

[github-actions]

PR Preview Action v1.8.1
🚀 View preview at https://instructure.design/pr-preview/pr-2551/
Built to branch gh-pages at 2026-05-12 13:30 UTC. Preview will be ready when the GitHub Pages deployment is complete.

[github-actions]

Visual regression report

✅ No changes.

Status	Count
Unchanged	32
Changed	0
New	0
Removed	0

📊 View full report

_{Baselines come from the visual-baselines branch. They refresh on every merge to master.}

[ToMESSKa]

@balzss I think this TopNavBar rework commit #2512 is missing from the table and TopNavBar v2 does not show the git history. Can you please look at this?

[git-nandor]

one split commit appears to have been missed — feat(many): rework TopNavBar (c1d18a6).

This commit introduced 33 new v2/* files (near-identical copies of their v1/* counterparts — the main index.tsx differs by only 2 lines) without a preceding synthetic rename, so all TopNavBar v2 files currently show only 1–2 unique blame commits.

This is likely not an oversight but an edge case in the detection heuristic.
In all 18 handled split commits (rework Img, rework Byline, etc.), both v1/* and v2/* files were added (A) in the same commit — they were created together from scratch. In the TopNavBar rework, v1/* files already existed and were only modified (M), while v2/* files were added (A). A heuristic looking for A+A pairs in the same commit would have missed this M+A case.

TopNavBar seems to be the only rework where the v1/ directory pre-existed; all others had v1/ and v2/ created together in the large add multi-version support commit.