From version control perspective: How to handle generated config files?

I just installed yiisoft/demo localy and run composer update, which generates a punch of config files within config/packages/yiisoft.

My IDE of course shows them as not checked in to the repo. So I was wondering how to deal with them?

1 Like

Check them into repo. We may change this behavior in the future but that’s under heavy discussion: Do not copy default configs · Issue #72 · yiisoft/config · GitHub

Ah ok. Is there a way to distinguish between an generated / default config file and an own config file?

Again, from version control perspective and mainly from my point of view, the ideal case would be,

to have all automatic generated / default config files not commited in into the repo

and the custom config files commited in into the repo.