To avoid the issue with recurrent update in the internal model, which may overwrite or force overwriting configurations or issues to update because is a Git tracked file with source code, I thought about the use of an environment or even JSON config file that is untracked by Git (gitignore) but shows an example file like .env.sample or config.json.sample.
I have no idea or Ruby to make it properly but maybe there is a gem such as Python DotEnv library to make it easier with environment files.
To avoid the issue with recurrent update in the internal model, which may overwrite or force overwriting configurations or issues to update because is a Git tracked file with source code, I thought about the use of an environment or even JSON config file that is untracked by Git (gitignore) but shows an example file like .env.sample or config.json.sample.
I have no idea or Ruby to make it properly but maybe there is a gem such as Python DotEnv library to make it easier with environment files.