Ability to suppress welcome message
See original GitHub issueThe "Welcome to .NET Core 3.0!.. " spiel adds considerable noise to CI logs.
While we can work around this by creating a file named "%HOME%/.dotnet/$(dotnet --version).dotnetFirstUseSentinel"
, this is hacky and adds noise to bulid configs.
It would be better to have a CLI option to suppress the message, e.g.
dotnet build --no-welcome
or
dotnet build --skip-first-time-experience
etc.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:25
- Comments:24 (15 by maintainers)
Top Results From Across the Web
How to remove the Welcome Message when a new ...
Re: How to remove the Welcome Message when a new member joins a group. · 1. Open Windows PowerShell command window as Administrator...
Read more >How to disable welcome message from Office 365 groups
The only way to remove the welcome message is connect to Exchange Online with PowerShell. First of all you have to install the...
Read more >Office 365 Group: How to Disable Welcome Email for new ...
Learn how to turn off welcome emails sent from Office 365 group, when adding new users. Follow these step-by-step instructions to disable the...
Read more >Chatbot - Ability to remove welcome message or change ...
This involves posing the welcome message as a question for us and adding quick replies.
Read more >Can I disable the welcome email notification for new end ...
Answer. You cannot disable welcome email notifications when your help center is enabled, and the account creation is initiated by the customer. ...
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
before dotnet-cli 3.0:
(aligns with other knobs
DOTNET_CLI_TELEMETRY_OPTOUT
etc.; many users including AppVeyor CI service were relying on it to keep the build job outputs clean)in 3.0 (since 3.0 RC2: https://github.com/dotnet/cli/commit/7efbf4770630fd370779d222ce9aba35ffe56100):
i think it would be just fine if
DOTNET_SKIP_FIRST_TIME_EXPERIENCE
is back in 3.1.Solved by dotnet/cli#13275