Keep Pi Git installs clean - #8
Merged
Merged
Conversation
Pi runs npm install for Git packages, which creates a root package-lock.json. Ignore that generated file so managed TreeWork checkouts stay clean and updateable.
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.
Summary
Pi runs
npm installafter cloning a Git package. The TreeWork root Pi manifest therefore produces an untracked rootpackage-lock.jsonin every managed checkout. Ignore only that root-generated lockfile sopi install git:github.com/Johnny-xuan/TreeWorkstays clean; the committedproject-map-ui/package-lock.jsonremains tracked.Verification
git diff --checkFollow-up to #7.