Please don't include generated files in source control.

What about lock files? ;)

oh yes please...
my boss always wants to include all those generated CSS and JS files just for the simple reason that he often forgets to start the build process when I send him a merge request for review...

tell that to 90% of JavaScript projects on GitHub.

What if the generated code is a machine learning model that takes days to train?

@jaread adding trained model to source control is not too bad, but there should be better ways. Stuff like git really only works well with text.

@timlyrics please enlighten me then, what version control system is more suited for models? Note that models are usually just a bunch of matrices.

Tell that to my retarded colleague who just committed the Pods directory

@ the one guy who keeps pushing his android build file so i have to clean gradle after every pull

Surely it depends on the type of generated file? 🤔

Well not everyone always builds on their server. For example for my app that is hosted on GitHub pages I have to push the compiled files.

@jaread Do you need those in version control? Storing those files appears to like storing a sql file for a database.

Yes, you need to be able to access from them somewhere. Yet I argue such files are better of in a datastore, whatever that may be. (Blob in a database, or stored on am amazon s3 cluster)