memdocs icon indicating copy to clipboard operation
memdocs copied to clipboard

Update create-orchestration-groups.md

Open dereklangMSFT opened this issue 9 months ago • 2 comments

Corrected the maximum script length to 16,383 characters and removed redundant references to obsolete Config Mgr versions

Internal work item for reference - https://msazure.visualstudio.com/Configmgr/_workitems/edit/24166622/?view=edit

dereklangMSFT avatar Apr 13 '25 12:04 dereklangMSFT

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

prmerger-automator[bot] avatar Apr 13 '25 12:04 prmerger-automator[bot]

Learn Build status updates of commit 80a8027:

:white_check_mark: Validation status: passed

File Status Preview URL Details
intune/configmgr/sum/deploy-use/create-orchestration-groups.md :white_check_mark:Succeeded

For more details, please refer to the build report.

For any questions, please:

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

prmerger-automator[bot] avatar Sep 09 '25 01:09 prmerger-automator[bot]

Hi,

This PR has been open for an extended period of time and has conflicts. If these changes are still relevant, please re-submit them to https://github.com/MicrosoftDocs/memdocs-pr.

Thanks, @v-smandalika

v-smandalika avatar Sep 16 '25 13:09 v-smandalika

Learn Build status updates of commit 80a8027:

: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 80a802703bf09cd4dcd81abd95611317ee7d30ff in branch patch-18 of repository https://github.com/dereklangMSFT/memdocs into branch main (commit cc00b881585b05978a5f32576cd24b00ce94a830). 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.