-
Notifications
You must be signed in to change notification settings - Fork 12
Added .gitignore and .editorconfig files #15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice works, few comments.
Ping once addressed, and we're good to go!
/site | ||
|
||
# mypy | ||
.mypy_cache/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add a newline at the end. It's a common standard to end files with a newline. https://stackoverflow.com/questions/729692/why-should-text-files-end-with-a-newline
.editorconfig
Outdated
insert_final_newline = true | ||
|
||
# 4 space indentation | ||
[*.{ini,py,py.tpl,rst}] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't have any ini
or .tpl
or .rst
files currently in the project.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please cross check what all files do we have currently in the repo, and adapt accordingly
.editorconfig
Outdated
indent_size = 4 | ||
|
||
# 4-width tabbed indentation | ||
[*.{sh,bat.tpl,Makefile.tpl}] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Again, there are no such files present. We can add such entries later once we have these files in the codebase. I hope you get the idea :)
It seems that your commit message doesn't contain enough information. Don't worry, most people don't know about good commit messages initially, including very experienced developers :) Standards vary from project to project. The most important part is the first line of your commit message - we can use it to read through a large number of commits and thus it's important that it's short but most importantly concise. I'd heartily recommend reading http://coala.io/commit ! To change your message you just use Cheers! |
Please now review my PR. I have made the changes requested by mentors. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A couple of changes in .editorconfig. Otherwise we're good to go 👍
@@ -0,0 +1,14 @@ | |||
# EditorConfig is awesome: http://EditorConfig.org |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't need this line :p
[*.{py}] | ||
indent_style = space | ||
indent_size = 4 | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is one extra line than blank line :)
Also, did you see #15 (comment) ? |
In what way I should change my commit message?? |
Commit 1
Commit 2
|
@pritamnegi I suggest you take a look at Github's gitignore as well to check if we need something more for our project. Also, make sure your PR description is informative enough. |
Ok as you say @realslimshanky |
#13