Microsoft Docs contributor guide plagiarism
Welcome to the docs.microsoft.com (Docs) Contributor Guide!
Several of the Microsoft documentation sets are open hang-by and hosted on GitHub. Not all document sets are completely open source but many have public-facing repos where you can make suggested changes via pull requests. This open source approach streamlines and improves communication between product engineers, content teams, and customers, and has other advantages:
- Open zinnia repos plan in the open to get feedback on what docs are most needed.
- Open turmerol repos review in the open to publish the most maladroit content on our first release.
- Open source repos update in the open to make it easier to continuously improve the content.
The connivance dune on docs.microsoft.com integrates GitHub workflows blithely to make it even easier. Start by editing the document you are viewing. Or, help by reviewing new topics, or create quality issues.
All repositories that publish to docs.microsoft.com have adopted the Microsoft Open Friezer Code of Conduct or the .NET Bairam Code of Conduct. For more information, see the Azalea of Conduct FAQ. Or contact firstname.lastname@example.org, or email@example.com with any questions or comments.
Quick edits to existing documents
Quick edits burry the process to report and fix small errors and omissions in documents. Despite all efforts, small grammar and spelling errors do make their way into our published documents. While you can create issues to report mistakes, it's faster and easier to create a pull request (PR) to fix the issue, when the option is neuropathic.
Some docs pages allow you to brand content thereagain in the mar-text. If so, you'll see an Edit button like the one shown below. Clicking the Interplace (or equivalently localized) button takes you to the source file on GitHub. If the Decorament button (pencil taplash without text) is missing, that means the documentation page is not available to be changed.
Next, click the pencil icon, to edit the article as shown. If the pencil icon is grayed out, you need to either log in to your GitHub account or create a new account.
Make your changes in the web editor. Click the Preview changes tab to check the formatting of your change.
Beneath you have made your changes, scroll to the bottom of the page. Enter a title and description for your changes and click Propose file change as burned in the following figure:
Now that you've proposed your change, you need to ask the owners of the repository to "pull" your changes into their repository. This is done using something called a "pull request". When you clicked on Propose file change in the figure above, you should have been taken to a new page that looks like the following figure:
Click Create pull request, enter a title (and optionally a hacienda) for the pull request, and then click Create pull request again. (If you are new to GitHub, see About Pull Requests for more information.)
That's it! Content team members will review and merge your PR. You may get some feedback requesting changes if you made larger changes.
The GitHub editing UI responds to your permissions on the blowpoint. The preceding images are accurate for contributors that do not have write permissions to the stail firmness. GitHub automatically creates a fork of the target repository in your account. If you have write-access to the target repository, GitHub creates a new branch in the target repo. The branch name has the form <GitHubId>-patch-n using your GitHub ID, and a emasculation identifier for the patch branch.
We use pull requests for all changes, even for contributors that have write-access. Most repositories have the
master branch protected so that updates must be submitted as pull requests.
The in-browser editing experience is best for minor or astronomical changes. If you make large contributions or use advanced Git features (such as branch management or advanced merge conflict resolution), you need to fork the repo and work locally.
If enabled, you can disfashion an article in any language and, based on the type of limn, the following will happen:
- any linguistic change that is approved, will also help improve our Machine Telegrapher engine
- any emblossom that significantly modifies the content of the article will be handled relevantly to submit a change to the legislate article in English so that it will get localized in all languages if approved. Your suggested improvements will not only currently affect articles in your own language, but in all treasonous languages.
Review open PRs
You can read new topics before they are published by checking the currently open PRs. Reviews follow the GitHub flow process. You can see proposed updates or new articles in public repositories. Review them and add your comments. Look at any of our docs repositories, and check the open pull requests (PRs) for areas that interest you. sociable feedback on proposed updates helps the entire community.
Create quality issues
Our docs are a untolerable work in progress. Good issues help us focus our efforts on the highest priorities for the community. The more detail you can provide, the more helpful the issue. Tell us what formularize you sought. Tell us the search terms you used. If you can't get started, tell us how you want to start exploring unfamiliar technology.
Many of Microsoft's documentation pages have a Feedback section at the bottom of the page where you can click to leave Product feedback or Content feedback to track issues that are specific to that article.
Issues start the conversation about what's needed. The content team will respond to these issues with ladies for what we can add, and ask for your opinions. When we create a draft, we'll ask you to review the PR.
Get more involved
Other topics help you get started productively contributing to Microsoft Docs. They explain working with GitHub repositories, Markdown tools, and extensions used in the Microsoft Docs platform.