Should the package-lock.json file be added to .gitignore?

It is highly recommended you commit the generated package lock to
source control: this will allow anyone else on your team, your
deployments, your CI/continuous integration, and anyone else who runs
npm install in your package source to get the exact same dependency
tree that you were developing on. Additionally, the diffs from these
changes are human-readable and will inform you of any changes npm has
made to your node_modules, so you can notice if any transitive
dependencies were updated, hoisted, etc.

Whitelist folder inside ignored folder

I have a node.js project with some node_modules. Now a node_module was not upto expectations and I manually changed, compiled and put it back into the node_module folder. I want to add this module to the GIT, however, the node_modules are listed in my gitignore (obviously). I tried the following /node_modules !/node_modules/the_module/** But files are … Read more

Best practices for adding .gitignore file for Python projects?

I’m trying to collect some of my default settings, and one thing I realized I don’t have a standard for is .gitignore files. There’s a great thread showing a good .gitignore for Visual Studio projects, but I don’t see many recommendations for Python and related tools (PyGTK, Django). So far, I have… *.pyc *.pyo …for … Read more