-
Notifications
You must be signed in to change notification settings - Fork 139
Format code blocks in Dynamo to Cosmos guide #318
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
base: main
Are you sure you want to change the base?
Conversation
Learn Build status updates of commit 4239feb: ✅ Validation status: passed
For more details, please refer to the build report. |
I'll reach out to my employeer about signing the CLA |
@microsoft-github-policy-service agree |
@89netraM : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR improves the readability of the Migrate your application from Amazon DynamoDB to Azure Cosmos DB article by formatting code blocks with proper indentation, spacing, and style conventions.
- Standardized JSON formatting with proper quotes and consistent indentation
- Applied C# coding conventions including consistent spacing, naming, and method formatting
- Improved SQL query formatting for better readability
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
Co-authored-by: Copilot <[email protected]>
Learn Build status updates of commit d5ad0f6: ✅ Validation status: passed
For more details, please refer to the build report. |
PRMerger Results
|
I've formatted the code blocks in the Migrate your application from Amazon DynamoDB to Azure Cosmos DB article.
For C# I've tried to follow I've tried to follow common formatting patterns as best I can.
This doesn't change any actual content, but makes the guide easier on the eyes.