Skip to content
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

Sync upcoming breaking changes docs from Azure/azure-powershell repo #2625

Closed
wants to merge 2 commits into from

Conversation

azure-powershell-bot
Copy link
Collaborator

Description

Sync latest upcoming breaking changes doc from Azure/azure-powershell repo.

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit 9dc338e:

✅ Validation status: passed

File Status Preview URL Details
docs-conceptual/azps-10.1.0 ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@github-actions
Copy link

github-actions bot commented Jul 3, 2023

Expectations

Thanks for your submission! Here's a quick note to provide you with some context for what to expect from the docs team and the process now that you've submitted a PR. Even if you've contributed to this repo before, we strongly suggest reading this information; it might have changed since you last read it.

To see our process for reviewing PRs, please read our editor's checklist and process for managing pull requests in particular. Below is a brief, high-level summary of what to expect, but our contributor guide has expanded details.

The docs team begins to review your PR if you request them to or if your PR meets these conditions:

  • It is not a draft PR.
  • It does not have a WIP prefix in the title.
  • It passes validation and build steps.
  • It does not have any merge conflicts.
  • You have checked every box in the PR Checklist, indicating you have completed all required steps and marked your PR as Ready to Merge.

You can always request a review at any stage in your authoring process, the docs team is here to help! You do not need to submit a fully polished and finished draft; the docs team can help you get content ready for merge.

While reviewing your PR, the docs team may make suggestions, write comments, and ask questions. When all requirements are satisfied, the docs team marks your PR as Approved and merges it. Once your PR is merged, it is included the next time the documentation is published. For this project, the documentation is published daily at 3 p.m. Pacific Standard Time (PST).

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit c8d9220:

✅ Validation status: passed

File Status Preview URL Details
docs-conceptual/azps-10.0.0/upcoming-breaking-changes.md ✅Succeeded View (azps-10.0.0)

For more details, please refer to the build report.

For any questions, please:

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit 60c57df:

✅ Validation status: passed

File Status Preview URL Details
docs-conceptual/azps-10.1.0 ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

mikefrobbins
mikefrobbins previously approved these changes Jul 6, 2023
Copy link
Contributor

@mikefrobbins mikefrobbins left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit 9067970:

❌ Validation status: errors

Please follow instructions here which may help to resolve issue.

File Status Preview URL Details
❌Error Details

  • [Error: CannotMergeCommit] Cannot merge commit 90679701bb7be0c3b521ce80fa33dccc0eecb24a in branch sync-upcoming-breaking-changes of repository https://github.com/MicrosoftDocs/azure-docs-powershell into branch main (commit 6a5001109383dafda498f48b340b459ac19ffa60). Please follow this documentation: https://help.github.com/articles/resolving-a-merge-conflict-using-the-command-line/ to use git.exe to resolve you content conflicts locally and then push to remote.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

@mikefrobbins
Copy link
Contributor

Replaced by PR #2635

@mikefrobbins mikefrobbins deleted the sync-upcoming-breaking-changes branch July 6, 2023 20:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants