Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/microsoftdocs/sccm-docs-powershell-ref
Configuration Manager PowerShell documentation public repo
https://github.com/microsoftdocs/sccm-docs-powershell-ref
mvldocs non-build officedocs powershell pubops
Last synced: 2 days ago
JSON representation
Configuration Manager PowerShell documentation public repo
- Host: GitHub
- URL: https://github.com/microsoftdocs/sccm-docs-powershell-ref
- Owner: MicrosoftDocs
- License: cc-by-4.0
- Created: 2018-10-26T20:25:36.000Z (about 6 years ago)
- Default Branch: main
- Last Pushed: 2024-11-05T11:29:28.000Z (about 2 months ago)
- Last Synced: 2024-12-17T15:22:52.197Z (9 days ago)
- Topics: mvldocs, non-build, officedocs, powershell, pubops
- Homepage: https://docs.microsoft.com/powershell/sccm/configurationmanager/
- Size: 13.1 MB
- Stars: 27
- Watchers: 35
- Forks: 62
- Open Issues: 35
-
Metadata Files:
- Readme: README.md
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
Awesome Lists containing this project
README
# Overview
## PowerShell Updatable Help (CabGen) CI Build Status
[/GitHub_MicrosoftDocs_sccm-docs-powershell/043980c6-04a3-6701-450a-495df201e8e7_cabgen_Publish-Updatable-Help?repoName=MicrosoftDocs%2Fsccm-docs-powershell&branchName=live)](https://apidrop.visualstudio.com/Content%20CI/_build/latest?definitionId=5078&repoName=MicrosoftDocs%2Fsccm-docs-powershell&branchName=live)
## Learn how to contribute
Anyone who is interested can contribute to the topics. When you contribute, your work will go directly into the content set after being merged. It will then be published to [Microsoft Learn](https://learn.microsoft.com/) and you will be listed as a contributor at: .
### Quickly update an article using GitHub.com
Contributors who only make infrequent or small updates can edit the file directly on GitHub.com without having to install any additional software. This article shows you how. [This two-minute video](https://www.microsoft.com/videoplayer/embed/RE1XQTG) also covers how to contribute.
1. Make sure you're signed in to GitHub.com with your GitHub account.
2. Browse to the page you want to edit on Microsoft Learn.
3. On the right-hand side of the page, click **Edit** (pencil icon).
4. The corresponding topic file on GitHub opens, where you need to click the **Edit this file** pencil icon.
5. The topic opens in a line-numbered editing page where you can make changes to the file. Files in GitHub are written and edited using Markdown language. For help on using Markdown, see [Mastering Markdown](https://guides.github.com/features/mastering-markdown/). Select the **Preview changes** tab to view your changes as you go.
6. When you're finished making changes, go to the **Propose file change** section at the bottom of the page:
- A brief title is required. By default, the title is the name of the file, but you can change it.
- Optionally, you can enter more details in the **Add an optional extended description** box.
When you're ready, click the green **Propose file change** button.
7. On the **Comparing changes** page that appears, click the green **Create pull request** button.
8. On the **Open a pull request** page that appears, click the green **Create pull request** button.
> [!NOTE]
> Your permissions in the repo determine what you see in the last several steps. People with no special privileges will see the **Propose file change** section and subsequent confirmation pages as described. People with permissions to create and approve their own pull requests will see a similar **Commit changes** section with extra options for creating a new branch and fewer confirmation pages.
The point is: click any green buttons that are presented to you until there are no more.
The writer identified in the metadata of the topic will be notified and will eventually review and approve your changes so the topic will be updated on Microsoft Learn. If there are questions or issues with the updates, the writer will contact you.
## Microsoft Open Source Code of Conduct
This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).
For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [[email protected]](mailto:[email protected]) with any additional questions or comments.
### Contributing
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit .
When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
### Legal Notices
Microsoft and any contributors grant you a license to the Microsoft documentation and other content in this repository under the [Creative Commons Attribution 4.0 International Public License](https://creativecommons.org/licenses/by/4.0/legalcode), see the [LICENSE](LICENSE) file, and grant you a license to any code in the repository under the [MIT License](https://opensource.org/licenses/MIT), see the [LICENSE-CODE](LICENSE-CODE) file.
Microsoft, Windows, Microsoft Azure and/or other Microsoft products and services referenced in the documentation may be either trademarks or registered trademarks of Microsoft in the United States and/or other countries.
The licenses for this project do not grant you rights to use any Microsoft names, logos, or trademarks. Microsoft's general trademark guidelines can be found at .
Privacy information can be found at
Microsoft and any contributors reserve all others rights, whether under their respective copyrights, patents, or trademarks, whether by implication, estoppel or otherwise.