`.lock` files in a public repository?

The CMS Questions
1

I’m not really familiar with github etc., but is it useful on https://github.com/getkirby/kitchensink in the sense of a “pattern template” especially for (future) developers to store various “.lock” files (among others as https://github.com/getkirby/kitchensink/blob/master/content/0_conditional-fields/.lock ) in the path https://github.com/getkirby/kitchensink/tree/master/content?

I know that these are automatically deleted when I use the panel of a website, but do these files belong in a public repository?

It may be possible to prevent this permanently by revising the https://github.com/getkirby/kitchensink/blob/master/.gitignore file. Then I suggest to revise this file “.gitignore” also in the other Kirby kits.

2

I believe you can safely ignore .lock files in your .gitignore files. These don’t belong in the repo and are only needed for the panel’s content locking feature.

3

@bvdputte:

Thanks to your answer.

But that does not solve the asked change at Github, if I’m correct.

4

@texnixe:

Thank you very much for the changes at Github in all three Kirby Kits. :heart: