Should I be adding the Django migration files in the .gitignore file?
You should think of migrations as a version control system for your database schema. makemigrations is responsible for packaging up your model changes into individual migration files - analogous to commits - and migrate is responsible for applying those to your database.
The migration files for each app live in a “migrations” directory inside of that app, and are designed to be committed to, and distributed as part of, its codebase. You should be making them once on your development machine and then running the same migrations on your colleagues’ machines, your staging machines, and eventually your production machines.
golden rule : Make once on dev and migrate on all
Should I be adding the Django migration files in the .gitignore file? 
I've recently been getting a lot of git issues due to migration conflicts and was wondering if I should be marking migration files as ignore. 
If so, how would I go about adding all of the migrations that I have in my apps, and adding them to the .gitignore file?