Add optional argument to dotnet new for adding .gitignore
See original GitHub issueIs 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 instance
dotnet new web --add-git
Issue Analytics
- State:
- Created a year ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Add optional argument to dotnet new for adding .gitignore
Once you have a symbol defined, you'd add a postAction that has a condition that checks the symbol you defined earlier. I'd suggest...
Read more >Easy to create .gitignore for the dotnet developers
Starting from SDK 3.0, there is a new parameter gitignore, which creates a dotnet gitignore file. The created file is a good starting...
Read more >Creating Project Templates for dotnet – Part 2 – Optional Files
For our example I'm going to add in a ReadMe.md, a License.txt, an .editorconfig, and a .gitignore file. ... dotnet new gitignore.
Read more >Create a template package for dotnet new - .NET
The dotnet new install command supports installing template packages ... The --output parameter creates the template for template package in ...
Read more >Make your own custom .NET Core templates - Craft Bakery
NET Core templates! Steps: Install prerequisite tools; Templating tool dotnet new; Create template; Test template; Add custom parameters; Pack ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
this is very much related to https://github.com/dotnet/templating/issues/3208 and https://github.com/dotnet/templating/issues/2771.
We decided it falls in scope of https://github.com/dotnet/templating/issues/3208 or https://github.com/dotnet/templating/issues/2771, but there is no definite timeline on that yet.