chore: [java] synthtool not to create an initial gitignore.#1672
Merged
suztomo merged 3 commits intogoogleapis:masterfrom Oct 27, 2022
Merged
chore: [java] synthtool not to create an initial gitignore.#1672suztomo merged 3 commits intogoogleapis:masterfrom
suztomo merged 3 commits intogoogleapis:masterfrom
Conversation
Given that new generated libraries will come to the Java monorepo going forward and that any new hand-written libraries can get a new .gitignore from humans, there's no need to automatically prepare .gitignore file.
lqiu96
approved these changes
Oct 27, 2022
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.
Given that new generated libraries will come to the Java monorepo going forward and that any new hand-written libraries can get a new .gitignore from humans, there's no need to automatically prepare .gitignore file.
Fixes googleapis/google-cloud-java#8683
Credit: @lqiu96 found the problematic line.