Workflow for Ember CLI, broccoli, beanstalk

I currently build projects with Ember CLI. This uses broccoli as the build tool / asset pipeline etc. So, my version control and deployment is through beanstalk / and I use gitTower much of the time to deal with git.

My issue is with tracking built files. So, my repo is dealing with new unique sheriff_djfklajfksajfiosjafioasfsa.css files and js files each time I commit.

I just keep deploying it live with beanstalk, but it seems like I shouldn't be committing those files, and maybe they should be generated locally, but not tracked in the repo - AND THEN... built on the server? or somehow passing them through but not committing them?

What's the new magic?