[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
18 times, most recently
from
5d2f2a5
to
2471b60
Compare
Merge 018590311e583b0e2927f15bf643c0b0d33ea786 into dd4ae36b067ae13af0816ca710d05bcd9b5aa442
azure-sdk
force-pushed
the
sdkAuto/31549/Azure.Communication.Messages
branch
from
2471b60
to
87c226d
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.