-
Notifications
You must be signed in to change notification settings - Fork 11
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
Improve gitignore file comments and organization. #70
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.
I don't like this. It's too dangerous, since it could exclude something important.
This feels to me like a personal preference that should be handled in your local global git
configuration. As a result I suggest closing this PR unmerged.
"It's a no from me dog."
Yes, It could exclude something important. But that is an easy fix. I'd rather err on the side of excluding something instead of including it. I'm fine with setting this in my globals if there is no value in this for anyone. I would like to merge the comments still since we do have people using the skeletons as their first interaction with |
I also like the comments and would like to add them. I don't have a strong preference, but would err on the side of the convenience exclusions as a personal setting. |
👆 |
af6d12a
to
18fd600
Compare
* Add a comment describing what the files does. * Add sections to organize patterns.
18fd600
to
ba49077
Compare
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.
💬
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.
👻
🗣 Description
Add a pattern that developers may use to quickly ignore files private to their development environment.💭 Motivation and context
I'd like to propose a pattern that we can use to quickly ignore files in our development environments.I've found that sometimes I have the need for a scratch file, or a configuration that I'm testing locally that I don't want to end up under version control.
I've been using*-mine.*
This allows me to have files likeTODO-mine.md
,docker-compose-mine.yml
, orsecrets-mine.json
to live locally without fear of them making it into the repo.A quick Google search didn't turn up any related proposals for something like this. We could also use*-ignoreme.*
,*-nocommit.*
,*-yourmom.*
Pros:
hexanitrodiphenylamine.py
Cons:
land-mine.yml
LICENSE-mine
Alternatives:
~/.gitignore_global
file, and thengit config --global core.excludesFile ~/.gitignore_global
🧪 Testing
Works for me!
📷 Screenshots (if appropriate)
✅ Checklist
to reflect the changes in this PR.