Thanks for contributing.
For the next time, can you run gulp or gulp build before you push it?
Since files in /public directory are automatically built, they should not be changed unless you changed stylesheet or core javascript files.

Sure thing. I tried doing that the past couple of times, but it looks as though 15+ files are changed after I run gulp even though I didn't touch them. Am I supposed to commit all of those modified files every time I make a change?

Never mind, this may not be your fault.
I will figure out how to automatically build those files when merging.

@parkjs814 https://libraries.io/npm/javascript-gulp-precommit
not sure but might help

@duaraghav8 Actually gulp should build after we merge the pull request, not before pushing it.
I don't know what to do hmm..

@parkjs814 We could use travis.

@TornjV Isn't travis only for the deployment to server?

@TornjV might be on to something: https://gist.github.com/domenic/ec8b0fc8ab45f39403dd

@TornjV @nem035, mhm that can be one possible solution.
I guess it is time to move to AWS or Heroku, there are too many limitations as well as this issue.

@parkjs814, so for future commits, should I run gulp before pushing, or just push files that I explicitly changed?

@jarettgross,
I figured out that there will be no difference whether you run gulp or not.
Don't worry about this issue, and just send a pull request.
I will care about it.
Sorry for the inconvenience.