chore: drop leftover generated website files - #54
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Removes two Next.js generated files (
website/next-env.d.ts,website/tsconfig.tsbuildinfo) accidentally re-added by the #53 squash merge, plus the now-deadwebsite/*block from.gitignore.Why
Housekeeping for the website extraction (#53). Supersedes an aborted branch whose commit accidentally staged node_modules (never merged, remote branch deleted).
How
git rmthe two files, remove the ignore block after deletingwebsite/from disk, staging verified to contain exactly three changes. No code change.Testing
Checklist
make lintpassesuv run python -m pytestis greenCHANGELOG.mdentry added under[Unreleased](n/a — housekeeping)type(scope): summaryRoadmap link: n/a — repo hygiene.