Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
The idea behind the .git/safe is that I run it manually and explicitly after I trust the directoy and the team behind the project. Creating it as part of the setup script defeats the point of that. Doing so without explcitly telling the user comes across as sneaky, perhaps. (I do expect all devs to read setup scripts before running them -- but I also know that they do not!) Switch this script to inform the user that they have no `.git/safe` directory but might like to make one. The warning output looks like this: ``` ~/thoughtbot/suspenders/foo% ./bin/setup The Gemfile's dependencies are satisfied Database 'foo_development' already exists Database 'foo_test' already exists W, [2017-04-28T10:29:08.973415 #29958] WARN -- : [SKYLIGHT] [1.2.1] Running Skylight in development mode. No data will be reported until you deploy your app. (To disable this message for all local apps, run `skylight disable_dev_warning`.) fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]' -- enable_extension("plpgsql") -> 0.0081s -- create_table("delayed_jobs", {:force=>:cascade}) -> 0.0618s -- initialize_schema_migrations_table() -> 0.0019s -- enable_extension("plpgsql") -> 0.0208s -- create_table("delayed_jobs", {:force=>:cascade}) -> 0.0328s -- initialize_schema_migrations_table() -> 0.0008s ----------------------------------------------------------------------- -> When you trust this repo, remember to run: mkdir -p .git/safe ~/thoughtbot/suspenders/foo% ```
- Loading branch information