deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-16 19:03:46 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Updated to include the CLA process

Browse Source
This commit is contained in:
LizRoss
2016-09-06 16:26:38 -07:00
parent 6fda4749e9
commit 0a186819f3
1 changed files with 15 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

27
windows/whats-new/contribute-to-a-topic.md
View File

@ -8,51 +8,54 @@ ms.sitesec: library
--- ---
# Edit an existing topic using the Contribute link # Edit an existing topic using the Contribute link
You can now make suggestions and update existing, public content with a GitHub account and a simple click of a link. You can now make suggestions and update existing, public content with a GitHub account and a simple click of a link.
**To edit a topic** **To edit a topic**
1. Go to the page on TechNet that you want to update, and then click **Contribute**. 1. All contributors who are ***not*** a Microsoft employee must [sign a Microsoft Contribution Licensing Agreement (CLA)](https://cla.microsoft.com/) before contributing to any Microsoft repositories.
If you've already contributed to Microsoft repositories in the past, congratulations!
You've already completed this step.
2. Go to the page on TechNet that you want to update, and then click **Contribute**.
![GitHub Web, showing the Contribute link](images/contribute-link.png) ![GitHub Web, showing the Contribute link](images/contribute-link.png)
2. Log into (or sign up for) a GitHub account. 3. Log into (or sign up for) a GitHub account.
You must have a GitHub account to get to the page that lets you edit a topic. You must have a GitHub account to get to the page that lets you edit a topic.
3. Click the **Pencil** icon (in the red box) to edit the content. 4. 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) ![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: 5. 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 Open Publishing Guide Home](http://aka.ms/windows-op-guide) - **If you're linked to the Microsoft organization in GitHub:** [Windows Open Publishing Guide Home](http://aka.ms/windows-op-guide)
- **If you're external to Microsoft:** [Mastering Markdown](https://guides.github.com/features/mastering-markdown/) - **If you're external to Microsoft:** [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. 6. Make your suggested change, and then click **Preview Changes** to make sure it looks correct.
![GitHub Web, showing the Preview Changes tab](images/preview-changes.png) ![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. 7. 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.
![GitHub Web, showing the Propose file change button](images/propose-file-change.png) ![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. 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. 8. On the **Comparing changes** screen, you’ll see if there are any problems with the file you’re checking in.
If there are no problems, you’ll see the message, **Able to merge**. If there are no problems, you’ll see the message, **Able to merge**.
![GitHub Web, showing the Comparing changes screen](images/compare-changes.png) ![GitHub Web, showing the Comparing changes screen](images/compare-changes.png)
8. Click **Create pull request**. 9. Click **Create pull request**.
9. Enter a title and description to give the approver the appropriate context about what’s in the request. 10. 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. 11. 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**. 12. Click **Create 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: 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: