search

chef / concrete

Concrete enhances your rebar based Erlang project by providing a common Makefile wrapper, a dialyzer make target that caches PLT analysis of your project's dependencies, and a mechanism to specify development only dependencies.
Apache License 2.0
56 stars 15 forks source link

The Fresh Repo Conundrum #27

Open joedevivo opened 10 years ago

joedevivo commented 10 years ago

You check out a fresh repo from github. it's empty, you're psyched. You want to concrete init but that command is really against creating anything if it didn't also create the directory.

➜  new_rep git:(master) ../concrete/concrete init .
ERROR: concrete init wants to create '.', but it already exists

I'll get around to this eventually, but I'll forget if I don't put it here.

seth commented 10 years ago

That's interesting. I've never thought to do it that way. I always have started with a local repo. So... concrete init. Then setup local git repo. Then create a repo on git and add the remote and then push.

Not opposed to making it work for other workflows thought for sure!

On Tue, Sep 9, 2014 at 1:43 PM, Joe DeVivo notifications@github.com wrote:

You check out a fresh repo from github. it's empty, you're psyched. You want to concrete init but that command is really against creating anything if it didn't also create the directory.

➜ new_rep git:(master) ../concrete/concrete init . ERROR: concrete init wants to create '.', but it already exists

I'll get around to this eventually, but I'll forget if I don't put it here.

— Reply to this email directly or view it on GitHub https://github.com/opscode/concrete/issues/27.