On Thu, Sep 15, 2016 at 9:01 AM, <is1637...@gmail.com> wrote: > I am wondering if generated source files from .proto files should be > checked into repository. >
Considered in isolation, checking generated artifacts into source control is discouraged <https://homes.cs.washington.edu/~mernst/advice/version-control.html#Dont_commit_generated_files> . But that lofty principle sometimes has to give way to reality and the specific circumstances in which you're working, the tools with which you are building your software, and the way you are distributing your software to your users. What tempts you to check files generated from your .proto files into your repository? How bothersome is it to avoid doing so? How bothersome will it be when your .proto files change to rerun the code generator and also change the generated files accordingly? I am particularly referring to python. > Thank you for including this detail although I'm not aware of anything about Python that would color the situation one way or the other. -N -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to grpc-io+unsubscr...@googlegroups.com. To post to this group, send email to grpc-io@googlegroups.com. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/CAEOYnAQ%2B%3DN%3DHEAtCQDcWL0%2B7rbsqf66wHZ89FrMd1u25nPD20A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
