divio bot deletes .divio/config.json

[viktor-yunenko]

Solutions

• use the divio CLI command to set up the project (divio project setup or divio project configure). divio project configure is used to add the config.json after a developer has already checked out the git repo on his local dev env.
• use the divio desktop app

Original report

Here's the type of the project that I created

• the repository - https://gitlab.com/effective-altruism/eahub-fider/
• the project - https://control.divio.com/control/71735/edit/88703/
• the cleanup commit by divio bot - https://gitlab.com/effective-altruism/eahub-fider/-/commit/db8458d9633f48a433ac0df4bd46e185f2921007

[viktor-yunenko]

Hi @evildmp, hi @GaretJax, could you help here perhaps? We heard that it could be disabled by using the empty template, but that doesn't seem to be the case?

cc @macolo

[macolo]

Divio Support feedback: .divio/config.json can contain user-specific data, that's why divio platform cannot allow the config.json in the git repository.

Workaround:

• use the divio CLI command to set up the project (divio project setup or divio project configure). divio project configure is used to add the config.json after a developer has already checked out the git repo on his local dev env.
• use the divio desktop app

[macolo]

@victor-yunenko do these work arounds work for you or do you have additional use cases?

[GaretJax]

@macolo elaborate a bit on the reasons, the .divio/config.json file can also contain project-specific data, and as it is possible to reuse the same source for multiple projects (e.g. forks pointing to the same external repo, separate FE/BE projects with the same codebase, etc), making it impractical to commit it to the repository.

[kinkerl]

we removed the logic around removing these files in the 2022-04-07 release. should be ok now.