-
-
Save santoshpy/6f982faf1eacdac153ffd86a3a694239 to your computer and use it in GitHub Desktop.
# Byte-compiled / optimized / DLL files | |
__pycache__/ | |
*.py[cod] | |
*$py.class | |
# C extensions | |
*.so | |
# Distribution / packaging | |
.Python | |
env/ | |
build/ | |
develop-eggs/ | |
dist/ | |
downloads/ | |
eggs/ | |
.eggs/ | |
lib/ | |
lib64/ | |
parts/ | |
sdist/ | |
var/ | |
wheels/ | |
*.egg-info/ | |
.installed.cfg | |
*.egg | |
# PyInstaller | |
# Usually these files are written by a python script from a template | |
# before PyInstaller builds the exe, so as to inject date/other infos into it. | |
*.manifest | |
*.spec | |
# Installer logs | |
pip-log.txt | |
pip-delete-this-directory.txt | |
# Unit test / coverage reports | |
htmlcov/ | |
.tox/ | |
.coverage | |
.coverage.* | |
.cache | |
nosetests.xml | |
coverage.xml | |
*.cover | |
.hypothesis/ | |
# Translations | |
*.mo | |
*.pot | |
# Django stuff: | |
*.log | |
local_settings.py | |
# Flask stuff: | |
instance/ | |
.webassets-cache | |
# Scrapy stuff: | |
.scrapy | |
# Sphinx documentation | |
docs/_build/ | |
# PyBuilder | |
target/ | |
# Jupyter Notebook | |
.ipynb_checkpoints | |
# pyenv | |
.python-version | |
# celery beat schedule file | |
celerybeat-schedule | |
# SageMath parsed files | |
*.sage.py | |
# dotenv | |
.env | |
# virtualenv | |
.venv | |
venv/ | |
ENV/ | |
.vscode | |
# Spyder project settings | |
.spyderproject | |
.spyproject | |
# Rope project settings | |
.ropeproject | |
# mkdocs documentation | |
/site | |
# mypy | |
.mypy_cache/ | |
.DS_Store | |
*.sqlite3 | |
media/ | |
*.pyc | |
*.db | |
*.pid | |
# Ignore Django Migrations in Development if you are working on team | |
# Only for Development only | |
# **/migrations/** | |
# !**/migrations | |
# !**/migrations/__init__.py |
Great. Thanks for the file.
Hi, why do you have migrations in your .gitignore file?
Hi, why do you have migrations in your .gitignore file?
if you are working on the git and sometimes you get a lot of git issues due to migration conflicts in development. It's not recommended for production.
Migration files are part of the code base and should be committed.
Migration files are part of the code base and should be committed.
Hello @opeerator
I agree but in some cases, due to migration conflict, I chose to ignore it.
Hello @santoshpurbey
What about data migrations?
Awesome
Hello @santoshpurbey
What about data migrations?
Thank you for pointing import stuff about database migrations, I've created this gist for my use-case where I've faced migrations issue while working with git so I put it in git ignore file but aware of this and only useful for development environment but not for production where we need the most. Interesting fact: unexpectedly this gist appeared on top in google search.
I have named my virtualenv in a different way like Eg: blogenv. So, how can I add that to gitignore file??
Can anyone help me out Please.....
I have named my virtualenv in a different way like Eg: blogenv. So, how can I add that to gitignore file??
Can anyone help me out Please.....
blogenv/
Hello, i have site-packages and py_cache files, should i ignore them on my gitignore, besides poluting my git status i feel like it is not necessary files, they should only remain on the user's side. What do you guys think ?
to be more precise they are /py_cache files and venv/lib/python/site-packages/ but i notice that you ignore the venv folder , we use a common venv in my team to not flood our machines and it works fine
I mean the venv is on the repo when you clone it. I am gonna remove it like suggested, but i would like to make a script to create the venv( i mean the activate/deactivate/... Binaries and so on)
Thanks a lot! Have a nice evening :)
Thank you so much this is really helpful...
thanks!
It's great, thanks!
Thanks it is really useful!
nice! tnx!