We are managing config development with Git, but using
tank push_configuration for the final deployment from our staging environment to the production environment. This means we have a .git folder in the config folder as follows:
> environment/ >> cache/ >> config/ >>> .git/ >>> core/ >>> and so on... >> install/ >> tank >> tank.bat
However, this means that every time we run
tank push_configuration, the
.git folder gets copied to the production environment, which we do not want.
I thought this would be addressed by rules in
config/core/schema/ignore_files, but obviously this only applies to folders created by Shotgun, not folders copied by tank.
Is there any way to configure tank not to push the