|
|
@@ -46,7 +46,7 @@ high quality, we request that contributions adhere to the following guidelines. |
|
|
|
|
|
|
|
- **Explain why you’re making a change**. Even if it seems self-evident, please |
|
|
|
take a sentence or two to tell us why your change or addition should happen. |
|
|
|
It’s especially helpful to articulate why this change applies to *everyone* |
|
|
|
It’s especially helpful to articulate why this change applies to _everyone_ |
|
|
|
who works with the applicable technology, rather than just you or your team. |
|
|
|
|
|
|
|
- **Please consider the scope of your change**. If your change is specific to a |
|
|
@@ -54,7 +54,7 @@ high quality, we request that contributions adhere to the following guidelines. |
|
|
|
template for that language or framework, rather than to the template for an |
|
|
|
editor, tool, or operating system. |
|
|
|
|
|
|
|
- **Please only modify *one template* per pull request**. This helps keep pull |
|
|
|
- **Please only modify _one template_ per pull request**. This helps keep pull |
|
|
|
requests and feedback focused on a specific project or technology. |
|
|
|
|
|
|
|
In general, the more you can do to help us understand the change you’re making, |
|
|
@@ -66,7 +66,7 @@ helpful than a simple `ls`. If it's not possible to curate a small set of |
|
|
|
useful rules, then the template might not be a good fit for this collection. |
|
|
|
|
|
|
|
Please also understand that we can’t list every tool that ever existed. |
|
|
|
Our aim is to curate a collection of the *most common and helpful* templates, |
|
|
|
Our aim is to curate a collection of the _most common and helpful_ templates, |
|
|
|
not to make sure we cover every project possible. If we choose not to |
|
|
|
include your language, tool, or project, it’s not because it’s not awesome. |
|
|
|
|