Should I be adding the Django migration files in the .gitignore file?
I can't imagine why you would be getting conflicts, unless you're editing the migrations somehow? That usually ends badly - if someone misses some intermediate commits then they won't be upgrading from the correct version, and their copy of the database will be corrupted.
The process that I follow is pretty simple - whenever you change the models for an app, you also commit a migration, and then that migration doesn't change - if you need something different in the model, then you change the model and commit a new migration alongside your changes.
In greenfield projects, you can often delete the migrations and start over from scratch with a 0001_ migration when you release, but if you have production code, then you can't (though you can squash migrations down into one).
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?