[AutoPR Azure.Communication.Messages] Adding interactive types to Advanced messaging #9841
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
azure-sdk
force-pushed
the
sdkAuto/31549/Azure.Communication.Messages
branch
29 times, most recently
from
fe79643
to
166eb82
Compare
azure-sdk
force-pushed
the
sdkAuto/31549/Azure.Communication.Messages
branch
8 times, most recently
from
35bc1b6
to
7285f16
Compare
Merge 6319afce622f77e234ce44a0a82f104bd165b2a4 into 01833dddcd59e369b08a8cad696f03297b18c045
azure-sdk
force-pushed
the
sdkAuto/31549/Azure.Communication.Messages
branch
from
7285f16
to
879958e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Create to sync Azure/azure-rest-api-specs#31549
Download the Azure.Communication.Messages package from here
This pull request has been automatically generated for preview purposes.