ADFA-5264: Stop tracking the test project's sync cache

[davidschachterADFA]

testing/resources/test-project/.cg/gradle-sync/{project.pb,sync.pb,sync.lock} were tracked, and a test run rewrites them with the local machine's absolute paths. So they show up modified in everyone's working tree, and a git add -A buries them in an unrelated commit — a 12.7 MB binary among them (12,678,925 bytes).

That is exactly how they last changed: the most recent commit touching them is an AI-plugin extraction refactor (#1441) that had no reason to. It happened to me this week too, which is what prompted the ticket.

They are a cache, not a fixture

ProjectSyncHelper writes them, and the only test that mentions the sync cache is GIVEN force sync not requested WHEN sync files are unreadable THEN sync anyway — it exercises their absence. Nothing reads a committed copy. A lock file was tracked as well.

Verified

With them untracked and ignored, :lsp:java:testV8DebugUnitTest — the suite that used to rewrite them — now leaves a clean working tree. Before this change that same run produced M …/project.pb and M …/sync.pb every time.

One thing found on the way, for ADFA-5068

:subprojects:tooling-api-impl is a java-library, so its tests have never run in CI — the aggregate task depends only on testV8DebugUnitTest, which is precisely the gap hal identified on #1643. And ToolingApiServerImplTest does not currently compile on stage: No value passed for parameter 'buildId'. Once #1643 closes the CI gap, that failure becomes visible, so it is worth knowing about in advance rather than as a surprise red build.

What this does not do

The blob stays in history — it entered in f01e558d6 (#1441) and remains reachable after this
deletion, so no clone or CI checkout gets smaller. This stops the file being rewritten by a test
run into everyone's working tree; shrinking the repo would need a history rewrite, which is not
in scope here.

Two follow-ups worth deciding on, both from review:

• Anyone with the file already modified needs git restore testing/resources/test-project/.cg
  before pulling, or git pull aborts with "Your local changes would be overwritten by merge" —
  which is most of us, since a test run is what modifies it.
• The rule is a hard-coded 4-segment path. .cg is SharedEnvironment.PROJECT_CACHE_DIR_NAME —
  always generated, never source — so a repo-wide .cg/ would be safe and would also cover
  gradle-plugin/src/test/resources/sample-project/.cg/ and testing/resources/sample-project/.cg/,
  neither of which is ignored today. The next test that syncs one of those repeats this incident.

[claude]

Claude Code Review

This repository is configured for manual code reviews. Comment @claude review for a one-time review, or @claude review always to subscribe this PR to a review on every future push.

_{Tip: disable this comment in your organization's Code Review settings.}

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 7a80e780-26f4-4b01-a7e9-78c3b9fb3f37

📥 Commits

Reviewing files that changed from the base of the PR and between ea658c3 and 8814aaa.

⛔ Files ignored due to path filters (1)

• testing/resources/test-project/.cg/gradle-sync/sync.lock is excluded by !**/*.lock

📒 Files selected for processing (3)

• .gitignore
• testing/resources/test-project/.cg/gradle-sync/project.pb
• testing/resources/test-project/.cg/gradle-sync/sync.pb

💤 Files with no reviewable changes (1)

• testing/resources/test-project/.cg/gradle-sync/sync.pb

Included review availability: Your plan provides up to 2 included reviews per hour; 1 remains after this review.

---

📝 Walkthrough

• Ignore generated .cg/gradle-sync/ cache files for the test project.
• Remove project.pb, sync.pb, and sync.lock from Git tracking.
• Prevent tests from creating machine-specific working-tree changes.
• Risk: The generated files remain in Git history because repository history was not rewritten.
• Risk: :subprojects:tooling-api-impl tests do not currently run in CI.
• Risk: ToolingApiServerImplTest does not compile on stage because buildId is missing.

Walkthrough

The change ignores the test project's .cg cache directory and removes its tracked Gradle synchronization metadata file.

Changes

Test project cache cleanup

Layer / File(s)	Summary
Ignore test project cache .gitignore	Adds comments and an ignore rule for testing/resources/test-project/.cg/. The tracked Gradle synchronization metadata file is removed.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 8814a

This change stops generated sync-cache files from being tracked or rewritten into developers' working trees. It is localized and merge-ready after normal checks, with no actionable merge-blocking risk remaining.

Suggested reviewers: hal-eisen-adfa, jatezzz

Poem

A rabbit found a cache tucked away

And marked it ignored today
Old sync notes hopped out of sight
The test project stayed clean and light
Carrots applaud the tidy byte

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the primary change: removing the test project's generated sync cache from tracking.
Description check	✅ Passed	The description directly explains why the generated sync cache must be untracked and ignored, how the change was verified, and what remains out of scope.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch task/ADFA-5264-sync-fixtures

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}