Refactor #96
closed
config/settings.yaml should not be under git control
Added by Martin Englund over 15 years ago.
Updated over 14 years ago.
Description
It is a host specific file which shouldn't be touched when you pull new changes.
Instead it should be distributed as config/settings.yaml.example
do you know of a way of removing it from git but not removing the file (for the people who do git pull?)
- Assignee set to Ohad Levy
just run
git mv config/settings.yaml config/settings.yaml.example
Martin Englund wrote:
just run
[...]
what about the people who already use it? :-\
I think you have to put in the release notes to re-create the settings.yaml file, as there is no way to ungit a file and still leave it (as far as I know, but I'm not a git expert, nor do I play one on TV)
btw, database.yml should also not be under git control
- Status changed from New to Closed
Also available in: Atom
PDF
Updated by 
Updated by