> However, some colleagues have the opinion that those conflicts are trivially resolved by rebuilding and thus don’t matter This is how mistakes happen, and w

> However, some colleagues have the opinion that those conflicts are trivially resolved by rebuilding and thus don’t matter This is how mistakes happen, and when dealing with things like serialisation is an absolute _minefield_ > nd having diffs of the generated code show up in pull requests adds value. They do have a point here, but is there a reason that the generated code diff couldn't be done separately to being commited? > What do others think, check in generated code or put it in gitignore? Always ignored, no questions asked. Generated code is a build artifact, the same way an object file or a jar is. It just happens to be human readable. Your build system should be 100% bulletproof and pick up changes to your input files and correctly regenerate the output files for you, anything less should be considered a p0 bugfix. If you need to cache these files for whatever reason, do so at a different level (sccache/container/whatever).