Closed real-guanyuming-he closed 3 months ago
@real-guanyuming-he please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
@microsoft-github-policy-service agree [company="{your company}"]
Options:
- (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.
@microsoft-github-policy-service agree
- (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.
@microsoft-github-policy-service agree company="Microsoft"
Contributor License Agreement
@microsoft-github-policy-service agree
Learn Build status updates of commit 8835470:
File | Status | Preview URL | Details |
---|---|---|---|
reference/docs-conceptual/community/contributing/pull-requests.md | :white_check_mark:Succeeded | View (>=powershell-5.1) | |
reference/docs-conceptual/dsc/overview.md | :white_check_mark:Succeeded | View (>=powershell-5.1) | |
reference/docs-conceptual/security/security-features.md | :white_check_mark:Succeeded | View (>=powershell-5.1) |
For more details, please refer to the build report.
For any questions, please:
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:
WIP
prefix in the title.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).
PR Summary
Fix a few typos in three documentations.
PR Checklist