Understanding .gitignore #42 #43
Conversation
|
Hi @rajwanur , really nice job on this! I recommend also calling out that files storing sensitive information (i.e. config.yml, .env) are commonly added to the .gitignore when running code locally that will utilize stored encrypted environmental variables once deployed. |
langkabh
left a comment
langkabh
left a comment
There was a problem hiding this comment.
Looks really good. I think it's complete, accurate and easy to read.
|
|
||
| Then add common patterns in .gitignore_global file located at ~/ (home directory) that should be ignored across all projects. | ||
|
|
||
| ## Important Limitation |
There was a problem hiding this comment.
I'm not sure I would call it a "limitation". You could also argue it's a "feature" that allows you to prevent a specific file from being ignored if you wish to track it despite instructions in the .gitignore. Or am I getting this wrong?
There was a problem hiding this comment.
I do agree that this is not a limitation. I have updated this section to call it 'Important Note' and described this as a feature.
… Note from Important Limitation.
|
@rajwanur I am happy to merge this now if you are |
|
@kieranjmartin I don't have any more changes in mind for this, so feel free to merge whenever you're ready. |
This pull request contains the draft of our new blog post "Understanding Gitignore" that addresses issue #42. The post explains what .gitignore is, how it works, and why it matters in version control.
I have not updated any styles, just the contents. Feel free to update the content or add styles.
Please review and provide feedback on:
Closes #42