Repository navigation
Conversation
- Untrack target/ (regenerated on build like .next/dist, avoiding merge conflicts) - Update .gitignore for target/, binaries, logs, OS files, and temp artifacts
This branch has not been deployed
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
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
Untracked
target/build files from git and added standard rules to.gitignore.Why?
Similar to
.nextordistin frontend projects,target/is dynamically regenerated on every run and duringmvn package. Tracking compiled binaries causes unnecessary repository bloat and merge conflicts.Key Changes
target/: Removed tracked binaries/classes from Git while keeping them intact locally..gitignore: Added rules fortarget/, binaries (*.jar), logs (*.log), JVM crash dumps, and OS/editor temp files (.DS_Store,Thumbs.db,*.swp).