-
Notifications
You must be signed in to change notification settings - Fork 25.2k
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
Finish PR: SignalR with Open AI #34636
Comments
@kevinguo-ed I've assigned @wadepickett to get #34636 merged. He'll pull in your commits to his PR so when it's merged you'll get credit. Hopefully you can answer any questions he has. |
@Rick-Anderson, Maybe you were thinking of the TOC item for SignalR samples... ...that points directly to the sample repo here: The sample for the doc in the PR is located here: Is the intent that the content in the PR would become a README type format for the sample and reside with the sample? Or it would become a README in /aspnet/SignalR-samples but point to microsoft/SignalR-Samples-AI/tree/main/AIStreaming. Thanks for any clarification. |
Yes. Mike's comment was not clear on this either. Since you were saying the same thing, I thought you might be able to clarify for my specific questions above. I will verify with Mike instead, but if you happen to know that's great. |
Description
@wadepickett pull in the commits in #33448 to your PR and finish this off. Please schedule for Feb or March
Manual port to ADO https://dev.azure.com/msft-skilling/Content/_workitems/edit/402618 and set label to seQuestered. -wp
(reQuest was not working at the time.)
Page URL
https://review.learn.microsoft.com/en-us/aspnet/core/tutorials/ai-powered-group-chat/ai-powered-group-chat?view=aspnetcore-8.0&branch=pr-en-us-33448&tabs=open-ai
Content source URL
https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/tutorials/ai-powered-group-chat/ai-powered-group-chat.md
Document ID
7bb9cdfd-b2c0-439f-3e65-fde31362724c
Article author
@kevinguo-ed
Metadata
Associated WorkItem - 402815
The text was updated successfully, but these errors were encountered: