-
Notifications
You must be signed in to change notification settings - Fork 4.1k
Update v4 new features doc with migration guide #28782
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
| Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status. |
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 adds a migration guide reference to the AutoRest PowerShell v4 features documentation. The change provides users with a direct link to migration instructions for transitioning from v3 to v4.
Key Changes
- Added a migration guide link at the beginning of the AutoRest PowerShell v4 features documentation
| @@ -1,4 +1,5 @@ | |||
| # Autorest PowerShell V4 Features from the End Users' Perspective | |||
| How to migrate from Autorest Powershell v3 to v4 please refer to [here](https://go.microsoft.com/fwlink/?linkid=2340250). | |||
Copilot
AI
Oct 31, 2025
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.
The capitalization of 'Powershell' is inconsistent with line 1. It should be 'PowerShell' (capital 'S').
| How to migrate from Autorest Powershell v3 to v4 please refer to [here](https://go.microsoft.com/fwlink/?linkid=2340250). | |
| How to migrate from Autorest PowerShell v3 to v4 please refer to [here](https://go.microsoft.com/fwlink/?linkid=2340250). |
| @@ -1,4 +1,5 @@ | |||
| # Autorest PowerShell V4 Features from the End Users' Perspective | |||
| How to migrate from Autorest Powershell v3 to v4 please refer to [here](https://go.microsoft.com/fwlink/?linkid=2340250). | |||
Copilot
AI
Oct 31, 2025
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.
The capitalization of 'Autorest' is inconsistent with line 1. It should be 'AutoRest' (capital 'R').
| How to migrate from Autorest Powershell v3 to v4 please refer to [here](https://go.microsoft.com/fwlink/?linkid=2340250). | |
| How to migrate from AutoRest Powershell v3 to v4 please refer to [here](https://go.microsoft.com/fwlink/?linkid=2340250). |
| @@ -1,4 +1,5 @@ | |||
| # Autorest PowerShell V4 Features from the End Users' Perspective | |||
| How to migrate from Autorest Powershell v3 to v4 please refer to [here](https://go.microsoft.com/fwlink/?linkid=2340250). | |||
Copilot
AI
Oct 31, 2025
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.
The sentence structure is awkward. Consider rephrasing to: 'For instructions on migrating from AutoRest PowerShell v3 to v4, please refer to this migration guide.' This improves clarity and provides better context for the link text.
| How to migrate from Autorest Powershell v3 to v4 please refer to [here](https://go.microsoft.com/fwlink/?linkid=2340250). | |
| For instructions on migrating from AutoRest PowerShell v3 to v4, please refer to [this migration guide](https://go.microsoft.com/fwlink/?linkid=2340250). |
Description
Mandatory Checklist
Please choose the target release of Azure PowerShell. (⚠️ Target release is a different concept from API readiness. Please click below links for details.)
Check this box to confirm: I have read the Submitting Changes section of
CONTRIBUTING.mdand reviewed the following information:ChangeLog.mdfile(s) appropriatelysrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.## Upcoming Releaseheader in the past tense.ChangeLog.mdif no new release is required, such as fixing test case only.