deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-12 05:17:22 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Update current contribution flow

Browse Source
This commit is contained in:
Anthony Swierkosz 2022-05-13 00:36:10 -04:00
parent ea7e0ff356
commit 57ef0fd5d7
No known key found for this signature in database
GPG Key ID: FA653BCC2CE12624
1 changed files with 39 additions and 43 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

36
CONTRIBUTING.md
View File

@ -2,7 +2,7 @@
Thank you for your interest in the Windows IT professional documentation! We appreciate your feedback, edits, and additions to our docs.
This page covers the basic steps for editing our technical documentation.
For a more up-to-date and general contribution guide, see the main [Microsoft Docs contributor guide overview.](https://docs.microsoft.com/contribute/)
For a more up-to-date and general contribution guide, see the main [Microsoft Docs contributor guide overview](https://docs.microsoft.com/contribute/).
## Sign a CLA
@ -17,48 +17,44 @@ We've tried to make editing an existing, public file as simple as possible.
>**Note**<br>
>At this time, only the English (en-us) content is available for editing.
**To edit a topic**
### To edit a topic
1. Go to the page on docs.microsoft.com that you want to update, and then click **Edit**.
1. Go to the page on [docs.microsoft.com](https://docs.microsoft.com/) that you want to update, and then select **Edit** (pencil icon).
![GitHub Web, showing the Edit link.](images/contribute-link.png)
![Microsoft Docs Web, showing the Edit link.](images/contribute-link.png)
2. Log into (or sign up for) a GitHub account.
2. On GitHub, Select the **Pencil** icon to edit the article. If the pencil icon is grayed out, you need to either log in to your GitHub account or create a new account.
You must have a GitHub account to get to the page that lets you edit a topic.
![GitHub Web, showing the Pencil icon.](images/pencil-icon.png)
3. Click the **Pencil** icon (in the red box) to edit the content.
![GitHub Web, showing the Pencil icon in the red box.](images/pencil-icon.png)
4. Using Markdown language, make your changes to the topic. For info about how to edit content using Markdown, see:
3. Using Markdown language, make your changes to the topic. For info about how to edit content using Markdown, see:
- **If you're linked to the Microsoft organization in GitHub:** [Windows authoring guide](https://aka.ms/WindowsAuthoring)
- **If you're external to Microsoft:** [Mastering Markdown](https://guides.github.com/features/mastering-markdown/)
- **If you're external to Microsoft:** [Microsoft Docs Markdown reference](https://docs.microsoft.com/contribute/markdown-reference), [Mastering Markdown](https://guides.github.com/features/mastering-markdown/)
5. Make your suggested change, and then click **Preview Changes** to make sure it looks correct.
4. Make your suggested change, and then select **Preview changes** to make sure it looks correct.
![GitHub Web, showing the Preview Changes tab.](images/preview-changes.png)
6. When you’re done editing the topic, scroll to the bottom of the page, and then click **Propose file change** to create a fork in your personal GitHub account.
5. When you’re done editing, scroll to the bottom of the page, and then select **Propose changes** to create a fork in your personal GitHub account.
![GitHub Web, showing the Propose file change button.](images/propose-file-change.png)
The **Comparing changes** screen appears to see what the changes are between your fork and the original content.
7. On the **Comparing changes** screen, you’ll see if there are any problems with the file you’re checking in.
6. On the **Comparing changes** screen, you’ll see if there are any problems with the file you’re checking.
If there are no problems, you’ll see the message, **Able to merge**.
![GitHub Web, showing the Comparing changes screen.](images/compare-changes.png)
8. Click **Create pull request**.
7. Select **Create pull request**.
9. Enter a title and description to give the approver the appropriate context about what’s in the request.
8. Enter a title and description to give the approver the appropriate context about what’s in the request.
10. Scroll to the bottom of the page, making sure that only your changed files are in this pull request. Otherwise, you could overwrite changes from other people.
9. Scroll to the bottom of the page, making sure that only your changed files are in this pull request. Otherwise, you could overwrite changes from other people.
11. Click **Create pull request** again to actually submit the pull request.
10. Click **Create pull request** again to actually submit the pull request.
The pull request is sent to the writer of the topic and your edits are reviewed. If your request is accepted, updates are published to one of the following places:
@ -82,7 +78,6 @@ We've tried to make editing an existing, public file as simple as possible.
- [Microsoft Desktop Optimization Pack](https://docs.microsoft.com/microsoft-desktop-optimization-pack)
## Making more substantial changes
To make substantial changes to an existing article, add or change images, or contribute a new article, you will need to create a local clone of the content.
@ -104,3 +99,4 @@ You can use your favorite text editor to edit Markdown. We recommend [Visual St
You can learn the basics of Markdown in just a few minutes. To get started, check out [Mastering Markdown](https://guides.github.com/features/mastering-markdown/).
Microsoft Docs uses several custom Markdown extensions. To learn more, see the [Microsoft Docs Markdown reference](https://docs.microsoft.com/contribute/markdown-reference).