Repository navigation
ng new --skip-git is ignored #7686
Copy link
Copy link
Closed
angular/devkit
#167Labels
P3An issue that is relevant to core functions, but does not impede progress. Important, but not urgentAn issue that is relevant to core functions, but does not impede progress. Important, but not urgentseverity3: broken
Description
Activity
- addedP3An issue that is relevant to core functions, but does not impede progress. Important, but not urgentAn issue that is relevant to core functions, but does not impede progress. Important, but not urgent
on Sep 22, 2017 - added 3 commits that reference this issue
on Sep 25, 2017 - added a commit that references this issue
on Sep 27, 2017 This was deliberate? 😱 Please see #8638 because I think there is a good use case for creating
.gitignorefile when it doesn't exist.- added a commit that references this issue
on Jun 6, 2018 angular-automatic-lock-bot commented
on Sep 7, 2019 More actionsThis issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.
- locked and limited conversation to collaborators
on Sep 7, 2019
Metadata
Metadata
Assignees
Labels
P3An issue that is relevant to core functions, but does not impede progress. Important, but not urgentAn issue that is relevant to core functions, but does not impede progress. Important, but not urgentseverity3: broken
Bug Report or Feature Request (mark with an
x)Versions.
@angular/cli: 1.4.1
node: 6.11.2
os: win32 x64
Repro steps.
Execute ng new --directory . --skip-git in a folder which already contains a .gitignore file reports the error. Alternatively execute ng new --skip-git and upon looking in the folder a .gitignore file is still created.
The log given by the failure.
error! .gitignore already exists.
Desired functionality.
The ng new command should comply with the --skip-git option and not attempt to create a .gitignore file.
This was not an issue is version 1.3.2 and therefore must be a regression bug