From 8aa5b77735f16bd07a53615fddce3533c052cbe1 Mon Sep 17 00:00:00 2001 From: Bradley White Date: Tue, 6 Feb 2018 15:19:16 -0500 Subject: [PATCH] Run CONTRIBUTING.md through mdformat. --- CONTRIBUTING.md | 26 +++++++++++++------------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 94abbcec..cf0912ea 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -4,19 +4,19 @@ the end). ### Before you contribute Before we can use your code, you must sign the [Google Individual Contributor -License Agreement] -(https://developers.google.com/open-source/cla/individual?csw=1) (CLA), which -you can do online. The CLA is necessary mainly because you own the copyright to -your changes, even after your contribution becomes part of our codebase, so we -need your permission to use and distribute your code. We also need to be sure of -various other things—for instance that you'll tell us if you know that -your code infringes on other people's patents. You don't have to sign the CLA -until after you've submitted your code for review and a member has approved it, -but you must do it before we can put your code into our codebase. Before you -start working on a larger contribution, you should get in touch with us first -through the issue tracker with your idea so that we can help out and possibly -guide you. Coordinating up front makes it much easier to avoid frustration later -on. +License +Agreement](https://developers.google.com/open-source/cla/individual?csw=1) +(CLA), which you can do online. The CLA is necessary mainly because you own the +copyright to your changes, even after your contribution becomes part of our +codebase, so we need your permission to use and distribute your code. We also +need to be sure of various other things—for instance that you'll tell us +if you know that your code infringes on other people's patents. You don't have +to sign the CLA until after you've submitted your code for review and a member +has approved it, but you must do it before we can put your code into our +codebase. Before you start working on a larger contribution, you should get in +touch with us first through the issue tracker with your idea so that we can help +out and possibly guide you. Coordinating up front makes it much easier to avoid +frustration later on. ### Code reviews