Skip to content

chore: stop tracking next-env.d.ts, which every build rewrites #862

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
blove merged 1 commit into from
Aug 30, 2026
Merged

chore: stop tracking next-env.d.ts, which every build rewrites #862

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions .gitignore
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,6 +36,10 @@ marketing/channels/marketing/cowork/outbox/dry-runs/
.next
out
.vercel
# Regenerated by every `next build` / `next dev`, and its contents differ
# between the two (dev writes ./.next/dev/types, build writes the Nx dist
# path). Tracking it means every build dirties the working tree.
apps/*/next-env.d.ts

# Whitepaper signup data
apps/website/data/
Expand Down
6 changes: 0 additions & 6 deletions apps/cockpit/next-env.d.ts
View file
Open in desktop

This file was deleted.

6 changes: 0 additions & 6 deletions apps/website/next-env.d.ts
View file
Open in desktop

This file was deleted.

Loading