Skip to content

chore: ignore build artifacts - #6

Merged
avocadoali merged 1 commit into
mainfrom
mihir/gitignore-build-artifacts
Aug 17, 2026
Merged

avocadoali merged 1 commit into
mainfrom
mihir/gitignore-build-artifacts

Conversation

@maharajamihir

Copy link
Copy Markdown
Contributor

.gitignore currently contains a single line, *.log. So in a checkout that has been built, git add -A stages the entire Rust target/ tree — about 5k files including a ~120 MB debug binary.

This bit me while preparing #5: the first commit swept in target/debug/labctl, and I only noticed because GitHub happened to be down when I tried to push.

Adds the generated directories:

  • /target — cargo build output
  • ui/node_modules/, ui/dist/ — the npm build; ui/ tracks only index.html, package.json and package-lock.json, and dist/ is what --features ui consumes at build time

Verified with git check-ignore -v that a probe file in each of the three paths is matched, and that git status is clean in a built checkout.

Split out of #5 to keep that one single-concern.

🤖 Generated with Claude Code

.gitignore covered only *.log, so a `git add -A` in a built checkout
stages the whole Rust target/ tree — ~5k files including a ~120 MB debug
binary. Add the generated directories: /target, and the UI's
node_modules/ and dist/ (ui/ tracks only index.html, package.json and
package-lock.json; dist/ is produced by the npm build that `--features ui`
consumes).

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@avocadoali
avocadoali merged commit 2f96b46 into main Aug 17, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants