hey, how do you keep up with the migration files and git branches, i name them, how do you make sure the current branch has latest migration files so it does not break your application :)

You should be following a guy workflow that everyone on your team is familiar with. My team keeps master branch that gets feature branched for bug fixes and new features. Each feature branch only holds one task item. After it is tested. Merge it back to the master. I maintain this same concept locally as well. This should create a map that has a single line from start of project, to the latest push, and a number of offshoots that always come back into the main line. If an offshoot does not, it is an abandoned branch, purposely or otherwise.

upper proposition is quite popular. We're also using develop brach, where we merge all feature braches so we can make more controlled releases. So we make release with couple of features. (auto deploy from master to production and from dev to staging server)