Should baked files be excluded from version control?

It dawned on me that it might be a good idea to have baked files ignored from version control. Is there a recommended best practice here?

I believe this really depends on your workflow and way you collaborate. The baked files are codegen, and coherence will generate them if they are missing (through the Editor). They will create noise in your commits if your schema is changing a lot. If you have a CI workflow that doesn’t automatically trigger coherence like the editor does, you will need to bake yourself as part of it, though. All things to consider!

Thanks for reply Brit. Those are good considerations. I’ll probably add the baked files to the ignore since it seems like the schema is changing pretty rapidly for me right now, resulting in a volume of “chore: baked new schema” commits.

For anyone who comes across this in the future, this is what I landed on in my .gitignore

# START Coherence Considerations

/[Aa]ssets/[Cc]oherence/[Bb]aked/*
/[Aa]ssets/[Cc]oherence/[Bb]aked.meta
/[Aa]ssets/[Cc]oherence/[Gg]athered.schema
/[Aa]ssets/[Cc]oherence/[Gg]athered.schema.meta

# END Coherence Considerations