Skip to content

Conversation

cephalin
Copy link
Contributor

No description provided.

Copy link
Contributor

@cephalin : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

@v-dirichards
Copy link
Contributor

refreshing the build

Copy link
Contributor

@Copilot Copilot AI left a 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 updates the author metadata in a troubleshooting documentation file from "genlin" to "JarrettRenshaw".

  • Updated author field in the YAML frontmatter

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

@v-dirichards v-dirichards reopened this Sep 30, 2025
@v-dirichards
Copy link
Contributor

Hi @ - Did you mean to open this PR in the private repo (azure-docs-pr)? If so, could you make this change in the private repo? We'll leave it open in case @genlin wants to review it.


@genlin Could you take a look? Thanks!

@v-dirichards
Copy link
Contributor

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged tracking label for the PR review team label Sep 30, 2025
Copy link
Contributor

Learn Build status updates of commit 934f56b:

❌ Validation status: errors

Please follow instructions here which may help to resolve issue.

File Status Preview URL Details
articles/migrate/assessment-prerequisites.md ❌Error Details
articles/migrate/assessment-properties.md ❌Error Details
articles/migrate/assessment-report.md ❌Error Details
articles/migrate/assessments-overview-migrate-to-azure-db-mysql.md ❌Error Details
articles/migrate/concepts-assessment-overview.md ❌Error Details
articles/migrate/concepts-overview.md ❌Error Details
articles/migrate/confidence-ratings.md ❌Error Details
articles/migrate/cost-estimation.md ❌Error Details
articles/migrate/create-mysql-assessment.md ❌Error Details
articles/migrate/create-web-app-assessment.md ❌Error Details
articles/migrate/how-to-create-assessment.md ❌Error Details
articles/migrate/how-to-create-sql-assessment.md ❌Error Details
articles/migrate/how-to-review-discovered-inventory.md ❌Error Details
articles/migrate/how-to-review-sql-assessment.md ❌Error Details
articles/migrate/onboard-to-azure-arc-with-azure-migrate.md ❌Error Details
articles/migrate/postgresql-assessment-properties.md ❌Error Details
articles/migrate/resource-tagging.md ❌Error Details
articles/migrate/review-application-assessment.md ❌Error Details
articles/migrate/review-assessment.md ❌Error Details
articles/migrate/review-azure-vmware-solution-assessment.md ❌Error Details
articles/migrate/review-sap-assessment.md ❌Error Details
articles/migrate/review-sql-assessment.md ❌Error Details
articles/migrate/review-web-app-assessment.md ❌Error Details
articles/migrate/supported-geographies.md ❌Error Details
articles/migrate/target-right-sizing.md ❌Error Details

This comment lists only the first 25 files in the pull request.

articles/migrate/assessment-prerequisites.md

  • Line 10, Column 15: [Error: moniker-range-out-of-scope] No moniker intersection between docfx.yml/docfx.json and file metadata. Config moniker range '<=migrate-classic >=migrate' is '', while file monikers is 'migrate'.

articles/migrate/assessment-properties.md

  • Line 10, Column 15: [Error: moniker-range-out-of-scope] No moniker intersection between docfx.yml/docfx.json and file metadata. Config moniker range '<=migrate-classic >=migrate' is '', while file monikers is 'migrate'.

articles/migrate/assessment-report.md

  • Line 10, Column 15: [Error: moniker-range-out-of-scope] No moniker intersection between docfx.yml/docfx.json and file metadata. Config moniker range '<=migrate-classic >=migrate' is '', while file monikers is 'migrate'.

articles/migrate/assessments-overview-migrate-to-azure-db-mysql.md

  • Line 9, Column 15: [Error: moniker-range-out-of-scope] No moniker intersection between docfx.yml/docfx.json and file metadata. Config moniker range '<=migrate-classic >=migrate' is '', while file monikers is 'migrate-classic'.

articles/migrate/concepts-assessment-overview.md

  • Line 10, Column 15: [Error: moniker-range-out-of-scope] No moniker intersection between docfx.yml/docfx.json and file metadata. Config moniker range '<=migrate-classic >=migrate' is '', while file monikers is 'migrate'.

articles/migrate/concepts-overview.md

  • Line 10, Column 15: [Error: moniker-range-out-of-scope] No moniker intersection between docfx.yml/docfx.json and file metadata. Config moniker range '<=migrate-classic >=migrate' is '', while file monikers is 'migrate'.

articles/migrate/confidence-ratings.md

  • Line 10, Column 15: [Error: moniker-range-out-of-scope] No moniker intersection between docfx.yml/docfx.json and file metadata. Config moniker range '<=migrate-classic >=migrate' is '', while file monikers is 'migrate'.

articles/migrate/cost-estimation.md

  • Line 10, Column 15: [Error: moniker-range-out-of-scope] No moniker intersection between docfx.yml/docfx.json and file metadata. Config moniker range '<=migrate-classic >=migrate' is '', while file monikers is 'migrate'.

articles/migrate/create-mysql-assessment.md

  • Line 10, Column 15: [Error: moniker-range-out-of-scope] No moniker intersection between docfx.yml/docfx.json and file metadata. Config moniker range '<=migrate-classic >=migrate' is '', while file monikers is 'migrate-classic'.

articles/migrate/create-web-app-assessment.md

  • Line 11, Column 15: [Error: moniker-range-out-of-scope] No moniker intersection between docfx.yml/docfx.json and file metadata. Config moniker range '<=migrate-classic >=migrate' is '', while file monikers is 'migrate'.

articles/migrate/how-to-create-assessment.md

  • Line 10, Column 15: [Error: moniker-range-out-of-scope] No moniker intersection between docfx.yml/docfx.json and file metadata. Config moniker range '<=migrate-classic >=migrate' is '', while file monikers is 'migrate'.

articles/migrate/how-to-create-sql-assessment.md

  • Line 11, Column 15: [Error: moniker-range-out-of-scope] No moniker intersection between docfx.yml/docfx.json and file metadata. Config moniker range '<=migrate-classic >=migrate' is '', while file monikers is 'migrate'.

articles/migrate/how-to-review-discovered-inventory.md

  • Line 12, Column 15: [Error: moniker-range-out-of-scope] No moniker intersection between docfx.yml/docfx.json and file metadata. Config moniker range '<=migrate-classic >=migrate' is '', while file monikers is 'migrate'.

articles/migrate/how-to-review-sql-assessment.md

  • Line 11, Column 15: [Error: moniker-range-out-of-scope] No moniker intersection between docfx.yml/docfx.json and file metadata. Config moniker range '<=migrate-classic >=migrate' is '', while file monikers is 'migrate'.

articles/migrate/onboard-to-azure-arc-with-azure-migrate.md

  • Line 10, Column 15: [Error: moniker-range-out-of-scope] No moniker intersection between docfx.yml/docfx.json and file metadata. Config moniker range '<=migrate-classic >=migrate' is '', while file monikers is 'migrate'.

articles/migrate/postgresql-assessment-properties.md

  • Line 9, Column 15: [Error: moniker-range-out-of-scope] No moniker intersection between docfx.yml/docfx.json and file metadata. Config moniker range '<=migrate-classic >=migrate' is '', while file monikers is 'migrate'.

articles/migrate/resource-tagging.md

  • Line 10, Column 15: [Error: moniker-range-out-of-scope] No moniker intersection between docfx.yml/docfx.json and file metadata. Config moniker range '<=migrate-classic >=migrate' is '', while file monikers is 'migrate'.

articles/migrate/review-application-assessment.md

  • Line 10, Column 15: [Error: moniker-range-out-of-scope] No moniker intersection between docfx.yml/docfx.json and file metadata. Config moniker range '<=migrate-classic >=migrate' is '', while file monikers is 'migrate'.

articles/migrate/review-assessment.md

  • Line 10, Column 15: [Error: moniker-range-out-of-scope] No moniker intersection between docfx.yml/docfx.json and file metadata. Config moniker range '<=migrate-classic >=migrate' is '', while file monikers is 'migrate'.

articles/migrate/review-azure-vmware-solution-assessment.md

  • Line 11, Column 15: [Error: moniker-range-out-of-scope] No moniker intersection between docfx.yml/docfx.json and file metadata. Config moniker range '<=migrate-classic >=migrate' is '', while file monikers is 'migrate'.

articles/migrate/review-sap-assessment.md

  • Line 11, Column 15: [Error: moniker-range-out-of-scope] No moniker intersection between docfx.yml/docfx.json and file metadata. Config moniker range '<=migrate-classic >=migrate' is '', while file monikers is 'migrate'.

articles/migrate/review-sql-assessment.md

  • Line 11, Column 15: [Error: moniker-range-out-of-scope] No moniker intersection between docfx.yml/docfx.json and file metadata. Config moniker range '<=migrate-classic >=migrate' is '', while file monikers is 'migrate'.

articles/migrate/review-web-app-assessment.md

  • Line 11, Column 15: [Error: moniker-range-out-of-scope] No moniker intersection between docfx.yml/docfx.json and file metadata. Config moniker range '<=migrate-classic >=migrate' is '', while file monikers is 'migrate'.

articles/migrate/supported-geographies.md

  • Line 7, Column 15: [Error: moniker-range-out-of-scope] No moniker intersection between docfx.yml/docfx.json and file metadata. Config moniker range '<=migrate-classic >=migrate' is '', while file monikers is 'migrate'.

articles/migrate/target-right-sizing.md

  • Line 9, Column 15: [Error: moniker-range-out-of-scope] No moniker intersection between docfx.yml/docfx.json and file metadata. Config moniker range '<=migrate-classic >=migrate' is '', while file monikers is 'migrate'.

This comment lists only the first 25 errors (including error/warning/suggestion) in the pull request.
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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants