fix(git-hooks): scope pre-push lint to branch-changed files only

[lisa-assistant]

Problem

The pre-push hook runs yarn lint, which ESLints all of packages/. On a monorepo with 70+ packages this is slow (~minutes) and extremely memory-hungry — in containers with ~4GB RAM it OOM-kills consistently.

Fix

Instead of linting all packages, lint only the files changed in the branch vs main, using git diff main...HEAD. This reuses the same getBranchChangedFiles() helper, getFilesToLint() filter, and runEslint() function already used by the pre-commit hook for staged files.

The result: lint time is proportional to the size of your change, not the size of the repo. A branch touching one file lints one file.

The build still runs in full (yarn build) so cross-package breakage from dependency changes is still caught. Lint still runs after build (not in parallel) to preserve the existing guarantee that template ESLint configs can require() dist output.

[netlify]

👷 Deploy request for cedarjs pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	c04c4f3

[greptile-apps]

Greptile Summary

The pre-push hook now lints only files changed against the local main branch while preserving build-before-lint ordering.

• Validates that the local main ref exists and reports diff failures instead of silently skipping lint.
• Routes template and create-cedar-rsc-app changes through their package-specific lint commands.
• Updates pre-push tests to mock branch-diff discovery and verify lint ordering and build-failure behavior.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains in the changed pre-push lint flow, and the previously reported issues are addressed by explicit Git-ref validation and package-aware lint routing.

Important Files Changed

Filename	Overview
tasks/git-hooks/tasks.mts	Adds checked branch-file discovery and scoped lint routing, resolving the previously reported silent skips, package-config bypasses, template TSX omission, and upstream-remote dependency.
tasks/git-hooks/tests/tasks.test.mts	Adapts pre-push ordering tests to the scoped ESLint invocation and isolates them from local Git ref and remote configuration.

_{Reviews (7): Last reviewed commit: "refactor(git-hooks): fail fast with a cl..." | Re-trigger Greptile}

[nx-cloud]

🤖 Nx Cloud AI Fix

Ensure the fix-ci command is configured to always run in your CI pipeline to get automatic fixes in future runs. For more information, please see https://nx.dev/ci/features/self-healing-ci

---

View your CI Pipeline Execution ↗ for commit c04c4f3

Command	Status	Duration	Result
nx run-many -t build:pack --exclude create-ceda...	✅ Succeeded	5s	View ↗
nx run-many -t build	✅ Succeeded	<1s	View ↗
nx run-many -t build --output-style=stream	✅ Succeeded	2m 48s	View ↗

💡 Verify your cache is correct by running tasks in a sandbox. Read docs ↗

---

☁️ Nx Cloud last updated this comment at 2026-07-27 16:15:15 UTC

[lisa-assistant]

Fixed both issues from Greptile:

1. Missing main ref — getBranchChangedFiles() now fetches main from upstream if it doesn't exist locally, ensuring the diff always succeeds instead of silently skipping lint.

2. Package-specific lint configs — Added runAllLint() which detects template/crwrsca changes and calls their dedicated lint:templates and lint:crwrsca commands instead of routing them through the root ESLint config.

[lisa-assistant]

Fixed three additional P1 issues:

1. Failed retry silently skips lint — Now checks fetch and retry diff status; throws error if either fails instead of silently swallowing stderr.

2. Template TSX changes bypass lint — Moved template/crwrsca change detection to run on original changedFiles list before filtering, since getFilesToLint() excludes template .tsx files by design.

3. Package-specific lint configs bypassed — Covered by the new runAllLint() logic that routes to appropriate lint commands based on which packages changed.

[lisa-assistant]

Fixed: getBranchChangedFiles() now tries multiple remotes (upstream, then origin) instead of hardcoding upstream. Falls back with a clear error message if main can't be fetched from any remote.

[lisa-assistant]

These P1 comments are all on earlier commits that I've now superseded with a simpler approach. The latest commit (c04c4f3) removes the multi-remote fetch-and-retry logic entirely and replaces it with a straightforward upfront check (git rev-parse --verify main) that either succeeds or fails with a clear, actionable error message telling the developer exactly what to run (git fetch origin main:main or upstream for forks).

This eliminates all three issues Greptile flagged:

• No more silent failures on fetch or retried diff
• No more template changes bypassing lint
• No more network-dependent or remote-name-dependent blocking logic

CI has already validated the fix with all checks passing (including both build-lint-test jobs on ubuntu and windows that were previously failing).

[github-actions]

The changes in this PR are now available on npm.

Try them out by running yarn cedar upgrade -t 6.0.0-canary.2782

Or try it in a new app with yarn dlx create-cedar-app@6.0.0-canary.2782