Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Initialize a new project only when no stack.yaml #3888

Merged
merged 2 commits into from Mar 14, 2018
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
3 changes: 3 additions & 0 deletions ChangeLog.md
Expand Up @@ -14,6 +14,9 @@ Behavior changes:
this itself since ghc-8.0.2, and Stack's attempted workaround for older
versions caused more problems than it solved.

* `stack new` no longer initializes a project if the project template contain
a stack.yaml file.

Other enhancements:

* A new sub command `ls` has been introduced to stack to view
Expand Down
4 changes: 3 additions & 1 deletion src/main/Main.hs
Expand Up @@ -935,7 +935,9 @@ newCmd :: (NewOpts,InitOpts) -> GlobalOpts -> IO ()
newCmd (newOpts,initOpts) go@GlobalOpts{..} =
withMiniConfigAndLock go $ do
dir <- new newOpts (forceOverwrite initOpts)
initProject IsNewCmd dir initOpts globalResolver
exists <- doesFileExist $ dir </> stackDotYaml
when (forceOverwrite initOpts || not exists) $
initProject IsNewCmd dir initOpts globalResolver

-- | List the available templates.
templatesCmd :: () -> GlobalOpts -> IO ()
Expand Down