From 1fddbf26f152826f9e95a65ae36e060e779f2ee2 Mon Sep 17 00:00:00 2001
From: Luke Latham <1622880+guardrex@users.noreply.github.com>
Date: Thu, 17 Nov 2022 13:13:11 -0600
Subject: [PATCH] Update holiday-blazor-comment.yml (#27672)

---
 .github/workflows/holiday-blazor-comment.yml | 17 +++++++++++++----
 1 file changed, 13 insertions(+), 4 deletions(-)

diff --git a/.github/workflows/holiday-blazor-comment.yml b/.github/workflows/holiday-blazor-comment.yml
index 924a8e6673..15cc26782a 100644
--- a/.github/workflows/holiday-blazor-comment.yml
+++ b/.github/workflows/holiday-blazor-comment.yml
@@ -16,9 +16,18 @@ jobs:
           issue-number: ${{ github.event.issue.number }}
           token: ${{ secrets.GITHUB_TOKEN }}
           body: |
-            # This is a multi-line test comment
+            ### 🍂🎁 ***OOF for the holidays*** ❄️⛄ 
             
-            A list:
+            This issue has been marked for triage on the `Blazor.Docs` project, and I'll respond as soon as I return. It make take a couple of days to dig out ⛰️⛏️ from holiday issues when I return, but I'll get back to you *ASAP* 🏃. 
             
-            * With GitHub **Markdown** :sparkles:
-            * Item 2
+            We only work on documentation on this repo. If you need product support, close this issue and seek assistance through one or more of the following support channels:
+            
+            * [Stack Overflow (tagged: `blazor`)](https://stackoverflow.com/questions/tagged/blazor)
+            * [General ASP.NET Core Slack Team](https://join.slack.com/t/aspnetcore/shared_invite/zt-1b60h73p0-PZPq3YCCaPbB21RcujMSVA)
+            * [Blazor Gitter](https://gitter.im/aspnet/Blazor)
+            
+            If you think that you found a potential bug in the framework or have product feedback, close this issue and open a new issue for the ASP.NET Core product unit at [dotnet/aspnetcore issues](https://github.com/dotnet/aspnetcore/issues). Bug reports require a clear explanation of the problem, usually including a minimal repro project placed on GitHub for the product unit engineers to download and run. If you determine with the product unit that it isn't a bug but merely requires documentation, please re-open this docs issue and place a cross-link to your engineering issue discussion. I'll take it up with you when I return from vacation.
+            
+            For problems or feedback on Visual Studio or Visual Studio for Mac, close this issue and use the [**Report a Problem**](https://docs.microsoft.com/visualstudio/ide/how-to-report-a-problem-with-visual-studio) or [**Suggest a Feature**](https://docs.microsoft.com/visualstudio/ide/suggest-a-feature) processes from within VS, which open internal issues for VS teams. For more information, see [Visual Studio Feedback](https://developercommunity.visualstudio.com/home) or [How to report a problem in Visual Studio for Mac](https://docs.microsoft.com/visualstudio/mac/report-a-problem).
+            
+            For problems with Visual Studio Code, close this issue and ask for support on community support forums. For bug reports and product feedback, open an issue on the [microsoft/vscode GitHub repo](https://github.com/microsoft/vscode/issues).