-
Notifications
You must be signed in to change notification settings - Fork 376
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
Add optional argument to dotnet new for adding .gitignore #6567
Comments
First step would be to identify the templates that should have this option. Only some of them are in this repo. You can check the README on the dotnet/templating repo for a more up-to-date list of repos that own specific templates - I try to keep that up to date. Then, for each project template that should have this option, you'd add a new Once you have a symbol defined, you'd add a postAction that has a |
Got it, so there isn't a universal template that all the other templates inherit from? I was thinking at the same level the output argument, but you are saying it needs to be done at every template. |
Correct - there's no inheritance here. Each template is an island. |
Got it. So this change will need to be in a few different repos than. I will take a look |
@vlada-shubina is there work being done in this space? I would hate to start the process of updating every template if there is a new process coming at some point. |
No, unfortunately there is no definite timeline for those features at the moment. |
@baronfel when I get to a point to test the templates, I assume I need to build them into a a nupack file from the repo the templates are in (for instance the aspnet repo)? Than build a new version of |
Is your feature request related to a problem? Please describe.
Based off of Twitter thread for folks
https://twitter.com/isaacrlevin/status/1571908208675147776
Describe the solution you'd like
Adding a new argument to
dotnet new
that will allow adding a.gitignore
to the output of the command. For instanceThe text was updated successfully, but these errors were encountered: