[storage/azure-storage-file-share] Fixed typos#25923
[storage/azure-storage-file-share] Fixed typos#25923jalauzon-msft merged 5 commits intoAzure:mainfrom
Conversation
|
Thank you for your contribution KdHyeon0661! We will review the pull request and get back to you soon. |
jalauzon-msft
left a comment
There was a problem hiding this comment.
Thanks @KdHyeon0661 for your contribution! It is really great to get CSpell running on file-share finally! Just two minor comments for your consideration, thanks!
sdk/storage/azure-storage-file-share/azure/storage/fileshare/_shared/policies.py
Show resolved
Hide resolved
Co-authored-by: wonhyeongseo <wonhseo@kakao.com>
|
This pull request is protected by Check Enforcer. What is Check Enforcer?Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass. Why am I getting this message?You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged. What should I do now?If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows: What if I am onboarding a new service?Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment: |
jalauzon-msft
left a comment
There was a problem hiding this comment.
Hi @KdHyeon0661, just a couple of small comments and this should be good. Looks like you'll also need to merge with main and resolve merge conflicts.
jalauzon-msft
left a comment
There was a problem hiding this comment.
Thanks @KdHyeon0661! This looks good now. Can you just merge main and resolve the conflicts and then I can merge this.
|
@KdHyeon0661, I pushed one small fix and merged this. Thanks for your contribution! |
Add 2023-11-01-preview for appplatform (Azure#26231) * Adds base for updating Microsoft.AppPlatform from version preview/2023-09-01-preview to version 2023-11-01-preview * Updates readme * Updates API version in new specs and examples * Fix go readme for asa api (Azure#25897) * Update language specific readme.md for 2023-11-01-preview api version (Azure#25898) * add more build result information in build resource (Azure#25930) Co-authored-by: 刘清仪 <liuqingyi@liuqingyideMacBook-Pro.local> * Add apiTryOutEnabledState for api protal (Azure#25923) * Add swagger for Spring Cloud Gateway response cache (Azure#25924) * Update appplatform.json (Azure#26234) * Update appplatform.json * Update appplatform.json --------- Co-authored-by: Sandy Cai <sandy.caiqing@gmail.com> Co-authored-by: Qingyi Liu <34502364+smile37773@users.noreply.github.com> Co-authored-by: 刘清仪 <liuqingyi@liuqingyideMacBook-Pro.local>
Description
closes #22680
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:
General Guidelines and Best Practices
Testing Guidelines