-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Updated Get-DistributionGroupMember.md-ADO-8426457 #11474
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
Conversation
Learn Build status updates of commit 3863469: ❌ Validation status: errorsPlease follow instructions here which may help to resolve issue.
exchange/exchange-ps/exchange/Get-DistributionGroupMember.md
exchange/exchange-ps/exchange/index.yml
This comment lists only the first 25 errors (including error/warning/suggestion) in the pull request. 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:
|
@chrisda Could you please guide how to resolve this error? ADO: https://office.visualstudio.com/MAX/_workitems/edit/8426457/ |
Learn Build status updates of commit 4e105bb: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
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.
Don't try to fix the lack of a carriage return between the H2s/H3s and text. All cmdlet reference topics suffer from this 'problem', because that's the way the platyPS utility currently creates them. I'd rather them all be the same for possible future global fix.
You can't just delete empty sections you don't like as that violates the schema. Nor can you simply put text anywhere you like (hence the massive cryptic validation errors). Typically, I would suggest adding that type of information in the DESCRIPTION section, except you can't use code blocks there (code inline is OK).Therefore, I just added it as a new example.
Improved description of new Example 3 per Issue #11474
@chrisda Thank you very much! Going forward, I will follow this guidelines for all cmdlet reference topics. |
No description provided.