You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unlike Java blueprint, for dotnetcore git repo is not automatically created for the generated codebase. Can you create a git repo at the root with the files that should be version controlled.
Motivation for or Use Case
Source control aspects are missing.
Reproduce the error
create a project by following: jhipster --blueprints dotnetcore
the following line appears after the npm command is run:
WARNING! The generated application could not be committed to Git, as a Git repository could not be initialized.
Suggest a Fix
create git repo for the generated code.
JHipster Version(s)
jHipster.NET v3.1.1
Browsers and Operating System
Windows 10.21H1
The text was updated successfully, but these errors were encountered:
Overview of the issue
Unlike Java blueprint, for dotnetcore git repo is not automatically created for the generated codebase. Can you create a git repo at the root with the files that should be version controlled.
Motivation for or Use Case
Source control aspects are missing.
Reproduce the error
create a project by following: jhipster --blueprints dotnetcore
the following line appears after the npm command is run:
WARNING! The generated application could not be committed to Git, as a Git repository could not be initialized.
Suggest a Fix
create git repo for the generated code.
JHipster Version(s)
jHipster.NET v3.1.1
Browsers and Operating System
Windows 10.21H1
The text was updated successfully, but these errors were encountered: