-
Notifications
You must be signed in to change notification settings - Fork 21
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
Restructure gitignore #51
base: main
Are you sure you want to change the base?
Conversation
Pull Request Test Coverage Report for Build 2184724951Warning: This coverage report may be inaccurate.This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
Details
💛 - Coveralls |
Is there a specific reason you prefer all caps? All caps are generally regarded as more difficult to read. One thing that's nice about the current organization is that the lineage from GitHub's default python project |
It is easier to tell sections apart, and distinguish form subsections. After all, we are not reading a whole paragraph in all-caps, but rather just a few words.
I was not aware of this, but it might be important overtime. Maybe we should have one section paralleling that file, and labeled accordingly to avoid future confusion; and other sections to add our own ignores. That would work for me as well. Thoughts? |
Summary
Redesign sectioning format and order in
.gitignore
, and add new ignore (i.e..venv/
).Details and comments
#
symbols as in the.md
format[...]
, as in.cfg
files