Add ignore file to cover build output #12
Conversation
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
Create a basic .gitignore file to cover the output files created by the build process.
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.
Create a basic .gitignore file to cover the output files created by the build process.
Before you merge this pull request
It's worth noting that while I'm a pretty advanced git user, I'm not an expert Java programmer (although I did write a program to evaluate arbitrarily complex arithmetic expressions involving multi-sided die roll notation -- think tabletop RPGs -- which is pretty nerdy even for a Java programmer :P) so I would recommend that if you do plan to merge this pull request, take a close look at the directories/patterns listed and make sure it's not getting anything that's not "build output"; you're almost certainly more familiar with the specifics of the Java build process than I am, so you may spot something that shouldn't be in there.