Resolve syncing conflicts from repo_sync_working_branch to main

learn-build-service-prod[bot] commented 2 weeks ago

Pull request opened by Docs to resolve syncing conflicts from repo_sync_working_branch to main.

learn-build-service-prod[bot] commented 2 weeks ago

Learn Build status updates of commit b04873e:

:x: Validation status: errors

Please follow instructions here which may help to resolve issue.

File	Status	Preview URL	Details
[]()	:x:Error		Details

[Error: CannotMergeCommit] Cannot merge commit b04873eef360826757ad16906c98116f9284c279 in branch repo_sync_working_branch of repository https://github.com/MicrosoftDocs/azure-docs into branch main (commit 211d3450211c26e95c6f40b4e01bd3adf5077774). 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:

Try searching the learn.microsoft.com contributor guides
Post your question in the Learn support channel

learn-build-service-prod[bot] commented 2 weeks ago

Learn Build status updates of commit b04873e:

:x: Validation status: errors

Please follow instructions here which may help to resolve issue.

File	Status	Preview URL	Details
[]()	:x:Error		Details

[Error: CannotMergeCommit] Cannot merge commit b04873eef360826757ad16906c98116f9284c279 in branch repo_sync_working_branch of repository https://github.com/MicrosoftDocs/azure-docs into branch main (commit 211d3450211c26e95c6f40b4e01bd3adf5077774). 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:

Try searching the learn.microsoft.com contributor guides
Post your question in the Learn support channel

learn-build-service-prod[bot] commented 2 weeks ago

Learn Build status updates of commit 03c1d39:

:x: Validation status: errors

Please follow instructions here which may help to resolve issue.

File	Status	Preview URL	Details
[]()	:x:Error		Details

[Error: CannotMergeCommit] Cannot merge commit 03c1d3954db2e760e6470090ca2eff2714c50898 in branch repo_sync_working_branch of repository https://github.com/MicrosoftDocs/azure-docs into branch main (commit 211d3450211c26e95c6f40b4e01bd3adf5077774). 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:

Try searching the learn.microsoft.com contributor guides
Post your question in the Learn support channel

Jak-MS commented 2 weeks ago

@huypub @tfosmark - bringing your attention to this failed repo_sync PR (due to merge conflicts) ... and noting that these conflicts cannot be resolved in the PR.

Also, to complicate things, this repo and it's private '-pr' counterpart are in content freeze. Relying on your good wisdom on how to proceed. thanks.

cc: @MicrosoftDocs/public-repo-pr-review-team

huypub commented 2 weeks ago

@Jak-MS The sync from the public to the private repo of azure-docs-pr is disabled since 5/08. So it is better that we come back to this after Build 2024 (5/21).

learn-build-service-prod[bot] commented 2 weeks ago

Learn Build status updates of commit 3fad646:

:x: Validation status: errors

Please follow instructions here which may help to resolve issue.

File	Status	Preview URL	Details
[]()	:x:Error		Details

[Error: CannotMergeCommit] Cannot merge commit 3fad646d8c8f1e6bf17e0727b1ab7b5ee1775847 in branch repo_sync_working_branch of repository https://github.com/MicrosoftDocs/azure-docs into branch main (commit 211d3450211c26e95c6f40b4e01bd3adf5077774). 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:

Try searching the learn.microsoft.com contributor guides
Post your question in the Learn support channel

learn-build-service-prod[bot] commented 2 weeks ago

Learn Build status updates of commit 48ade3a:

:x: Validation status: errors

Please follow instructions here which may help to resolve issue.

File	Status	Preview URL	Details
[]()	:x:Error		Details

[Error: CannotMergeCommit] Cannot merge commit 48ade3a792fbaef96838883c52efe424e2f0a9f1 in branch repo_sync_working_branch of repository https://github.com/MicrosoftDocs/azure-docs into branch main (commit 211d3450211c26e95c6f40b4e01bd3adf5077774). 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:

Try searching the learn.microsoft.com contributor guides
Post your question in the Learn support channel

learn-build-service-prod[bot] commented 1 week ago

Learn Build status updates of commit 68f1297:

:x: Validation status: errors

Please follow instructions here which may help to resolve issue.

File	Status	Preview URL	Details
[]()	:x:Error		Details

[Error: CannotMergeCommit] Cannot merge commit 68f1297fa0295ee14596d66c649e465671ab86e1 in branch repo_sync_working_branch of repository https://github.com/MicrosoftDocs/azure-docs into branch main (commit 211d3450211c26e95c6f40b4e01bd3adf5077774). 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:

Try searching the learn.microsoft.com contributor guides
Post your question in the Learn support channel

learn-build-service-prod[bot] commented 1 week ago

Learn Build status updates of commit b1020a7:

:x: Validation status: errors

Please follow instructions here which may help to resolve issue.

File	Status	Preview URL	Details
[]()	:x:Error		Details

[Error: CannotMergeCommit] Cannot merge commit b1020a731cc1de60135b38b46bea6ac60fc7ffb9 in branch repo_sync_working_branch of repository https://github.com/MicrosoftDocs/azure-docs into branch main (commit 211d3450211c26e95c6f40b4e01bd3adf5077774). 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:

Try searching the learn.microsoft.com contributor guides
Post your question in the Learn support channel

learn-build-service-prod[bot] commented 1 week ago

Learn Build status updates of commit fe54a7d:

:bulb: Validation status: suggestions

File	Status	Details
articles/ai-services/computer-vision/computer-vision-how-to-install-containers.md	:bulb:Suggestion	Details
articles/ai-services/computer-vision/concept-background-removal.md	:bulb:Suggestion	Details
articles/ai-services/computer-vision/concept-shelf-analysis.md	:bulb:Suggestion	Details
articles/ai-services/computer-vision/how-to/shelf-analyze.md	:bulb:Suggestion	Details
articles/ai-services/computer-vision/how-to/shelf-model-customization.md	:bulb:Suggestion	Details
articles/ai-services/computer-vision/how-to/shelf-planogram.md	:bulb:Suggestion	Details
articles/ai-services/computer-vision/language-support.md	:bulb:Suggestion	Details
articles/ai-services/computer-vision/sdk/overview-sdk.md	:bulb:Suggestion	Details
articles/ai-services/computer-vision/toc.yml	:bulb:Suggestion	Details
articles/ai-services/computer-vision/whats-new.md	:bulb:Suggestion	Details
articles/ai-services/custom-vision-service/copy-move-projects.md	:bulb:Suggestion	Details
articles/ai-services/custom-vision-service/includes/quickstarts/rest-tutorial.md	:bulb:Suggestion	Details
articles/ai-services/custom-vision-service/select-domain.md	:bulb:Suggestion	Details
articles/ai-services/custom-vision-service/storage-integration.md	:bulb:Suggestion	Details
articles/ai-services/custom-vision-service/toc.yml	:bulb:Suggestion	Details
articles/ai-services/custom-vision-service/use-prediction-api.md	:bulb:Suggestion	Details
articles/ai-studio/how-to/develop/sdk-overview.md	:bulb:Suggestion	Details
.openpublishing.publish.config.json	:white_check_mark:Succeeded
.openpublishing.redirection.api-center.json	:white_check_mark:Succeeded
.openpublishing.redirection.azure-kubernetes-service.json	:white_check_mark:Succeeded
.openpublishing.redirection.azure-monitor.json	:white_check_mark:Succeeded
.openpublishing.redirection.json	:white_check_mark:Succeeded
.openpublishing.redirection.operator-service-manager.json	:white_check_mark:Succeeded
.openpublishing.redirection.sentinel.json	:white_check_mark:Succeeded
articles/active-directory-b2c/microsoft-graph-operations.md	:white_check_mark:Succeeded

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

articles/ai-services/computer-vision/computer-vision-how-to-install-containers.md

Line 347, Column 16: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /rest/api/computervision/operation-groups?view=rest-computervision-v3.2-preview

articles/ai-services/computer-vision/concept-background-removal.md

Line 55, Column 57: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /rest/api/computervision/image-analysis/segment?view=rest-computervision-2023-02-01-preview&tabs=HTTP

articles/ai-services/computer-vision/concept-shelf-analysis.md

Line 186, Column 3: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /rest/api/computervision/operation-groups?view=rest-computervision-2023-04-01-preview

articles/ai-services/computer-vision/how-to/shelf-analyze.md

Line 158, Column 3: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /rest/api/computervision/operation-groups?view=rest-computervision-2023-04-01-preview

articles/ai-services/computer-vision/how-to/shelf-model-customization.md

Line 71, Column 3: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /rest/api/computervision/operation-groups?view=rest-computervision-2023-04-01-preview

articles/ai-services/computer-vision/how-to/shelf-planogram.md

Line 303, Column 3: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /rest/api/computervision/operation-groups?view=rest-computervision-2023-04-01-preview

articles/ai-services/computer-vision/language-support.md

Line 130, Column 22: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /rest/api/computervision/analyze-image?view=rest-computervision-v3.1

articles/ai-services/computer-vision/sdk/overview-sdk.md

Line 25, Column 218: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /rest/api/computervision/operation-groups?view=rest-computervision-2023-04-01-preview
Line 28, Column 339: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /rest/api/computervision/operation-groups?view=rest-computervision-2023-04-01-preview

articles/ai-services/computer-vision/toc.yml

Line 82, Column 13: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /rest/api/computervision/operation-groups?view=rest-computervision-v3.2-preview
Line 84, Column 13: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /rest/api/computervision/operation-groups?view=rest-computervision-v3.1
Line 86, Column 13: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /rest/api/computervision/operation-groups?view=rest-computervision-v2.1
Line 248, Column 15: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /rest/api/computervision/operation-groups?view=rest-computervision-2023-04-01-preview
Line 274, Column 15: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /rest/api/computervision/operation-groups?view=rest-computervision-v3.1
Line 276, Column 15: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /rest/api/computervision/operation-groups?view=rest-computervision-v2.1

articles/ai-services/computer-vision/whats-new.md

Line 37, Column 216: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /rest/api/computervision/operation-groups?view=rest-computervision-2023-04-01-preview
Line 40, Column 336: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /rest/api/computervision/operation-groups?view=rest-computervision-2023-04-01-preview

articles/ai-services/custom-vision-service/copy-move-projects.md

Line 17, Column 7: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /rest/api/customvision/training/projects/export?view=rest-customvision-training-v3.3&tabs=HTTP
Line 17, Column 127: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /rest/api/customvision/training/projects/import?view=rest-customvision-training-v3.3&tabs=HTTP
Line 42, Column 14: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /rest/api/customvision/training/projects/get?view=rest-customvision-training-v3.3&tabs=HTTP
Line 80, Column 8: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /rest/api/customvision/training/projects/export?view=rest-customvision-training-v3.3&tabs=HTTP
Line 105, Column 8: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /rest/api/customvision/training/projects/import?view=rest-customvision-training-v3.3&tabs=HTTP

articles/ai-services/custom-vision-service/includes/quickstarts/rest-tutorial.md

Line 45, Column 102: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /rest/api/customvision/training/projects/create?view=rest-customvision-training-v3.3&tabs=HTTP
Line 102, Column 152: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /rest/api/customvision/training/images/create-from-data?view=rest-customvision-training-v3.3&tabs=HTTP
Line 121, Column 48: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /rest/api/customvision/training/projects/train?view=rest-customvision-training-v3.3&tabs=HTTP

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.

For any questions, please:

Try searching the learn.microsoft.com contributor guides
Post your question in the Learn support channel

prmerger-automator[bot] commented 1 week ago

PRMerger Results

Issue	Description
Added File(s)	This PR contains added files. New files require human review.
Deleted File(s)	This PR deletes Markdown or YAML files owned by another author, or json file(s). The pull request must contain a comment from the pull request author confirming that all the file deletions are intentional before the pull request can be merged.
Yaml File(s)	This PR includes changes to .yml file(s) owned by another author.
Changed Files	This PR contains more than 10 changed files.
Commits Count	This PR contains more than 15 commits.
File Change Percent	This PR contains file(s) with more than 30% file change.
GDPR Content(s)	PR references GDPR and must be human reviewed to ensure appropriate guidelines are followed.
Image File	This PR added or updated an image file(s).
Json File	This PR contains json file(s).
Repository root file	This pull request contains a file submitted to the root of the repository.

MicrosoftDocs / azure-docs