Refactor #96
config/settings.yaml should not be under git control
| Status: | Closed | Start: | 11/27/2009 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: |  Ohad Levy |
% Done: | 0% |
|
| Category: | - | |||
| Target version: | - | |||
| Backlog: | Difficulity: | |||
| Votes: | 0 |
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
Related issues
| duplicates Foreman - Refactor #343: settings file should not be under version control | Closed | 07/06/2010 |
History
Updated by Ohad Levy over 2 years ago
do you know of a way of removing it from git but not removing the file (for the people who do git pull?)
Updated by Martin Englund over 2 years ago
- Assigned to set to Ohad Levy
just run
git mv config/settings.yaml config/settings.yaml.example
Updated by Ohad Levy over 2 years ago
Martin Englund wrote:
just run [...]
what about the people who already use it? :-\
Updated by Martin Englund over 2 years ago
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)
Updated by Ohad Levy over 1 year ago
- Status changed from New to Closed
