Add editorconfig and gitignore files #21
Open
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
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.
These files are necessary for the following reasons:
With the .gitignore file git ignores the build folder and all it's content. Really necessary when you need to keep your development environment clean of the build files.
With the .editorconfig you set the standard of how the files are going to be written, if spaces or tabs are used and how much will they indent in characters. Really necessary for projects were a team is developing in parallel. I added here some standards, but these might be different on what the team uses. Feel free to change them.
The Pull Request is a proposal. Feel free to ignore it if you don't find it useful.