chore: Add missing .gitignore with Maven target/ - #757
Closed
vorburger wants to merge 1 commit into
Closed
Conversation
|
Hi @vorburger , Thank you for your contributions. Kindly provide the description of this PR. |
Contributor
Author
@hemasekhar-p sure thing - done! |
Contributor
Author
|
@hemasekhar-p merge? |
vorburger
added a commit
to vorburger/dotfiles
that referenced
this pull request
Feb 1, 2026
Because googleapis/java-genai#757 is being ignored.
copybara-service Bot
pushed a commit
that referenced
this pull request
Aug 24, 2026
Ignore the target/ build output directory in Git workspaces. This prevents Maven build artifacts from appearing as untracked or dirty files in Git and downstream tooling. Ported from #757. PiperOrigin-RevId: 964723612
copybara-service Bot
pushed a commit
that referenced
this pull request
Aug 25, 2026
Ignore the target/ build output directory in Git workspaces. This prevents Maven build artifacts from appearing as untracked or dirty files in Git and downstream tooling. Ported from #757. PiperOrigin-RevId: 964723612
copybara-service Bot
pushed a commit
that referenced
this pull request
Aug 25, 2026
Ignore the target/ build output directory in Git workspaces. This prevents Maven build artifacts from appearing as untracked or dirty files in Git and downstream tooling. Ported from #757. PiperOrigin-RevId: 964723612
copybara-service Bot
pushed a commit
that referenced
this pull request
Aug 26, 2026
Ignore the target/ build output directory in Git workspaces. This prevents Maven build artifacts from appearing as untracked or dirty files in Git and downstream tooling. Ported from #757. PiperOrigin-RevId: 964723612
copybara-service Bot
pushed a commit
that referenced
this pull request
Aug 26, 2026
Ignore the target/ build output directory in Git workspaces. This prevents Maven build artifacts from appearing as untracked or dirty files in Git and downstream tooling. Ported from #757. FUTURE_COPYBARA_INTEGRATE_REVIEW=#1205 from googleapis:release-please--branches--main e684dd0 PiperOrigin-RevId: 964723612
Contributor
Author
|
Closing as duplicate of #1196. |
copybara-service Bot
pushed a commit
that referenced
this pull request
Aug 26, 2026
Ignore the target/ build output directory in Git workspaces. This prevents Maven build artifacts from appearing as untracked or dirty files in Git and downstream tooling. Ported from #757. PiperOrigin-RevId: 971528724
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
2 participants
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.
Add the missing
.gitignorefile containingtarget/so that contributors don't see files built by Maven as "dirty" in their Git workspace, and don't accidentally add them to commits.Furthermore, the presence of this
.gitignorefile can be leveraged by various tools, including but not limited to AI coding tools, to understand that everything under thetarget/can be ignored by such tools.