|
3 | 3 | We would love for you to contribute to Nest and help make it even better than it is |
4 | 4 | today! As a contributor, here are the guidelines we would like you to follow: |
5 | 5 |
|
6 | | -* [Code of Conduct](#coc) |
| 6 | +<!--* [Code of Conduct](#coc)--> |
7 | 7 | * [Question or Problem?](#question) |
8 | 8 | * [Issues and Bugs](#issue) |
9 | 9 | * [Feature Requests](#feature) |
@@ -76,10 +76,15 @@ You can file new issues by filling out our [new issue form](https://github.com/n |
76 | 76 |
|
77 | 77 | Before you submit your Pull Request (PR) consider the following guidelines: |
78 | 78 |
|
| 79 | +<!-- |
| 80 | +To the first point |
| 81 | +
|
| 82 | +1. Please sign our [Contributor License Agreement (CLA)](#cla) before sending PRs. |
| 83 | +We cannot accept code without this. |
| 84 | +--> |
| 85 | + |
79 | 86 | 1. Search [GitHub](https://github.com/nestjs/nest/pulls) for an open or closed PR |
80 | 87 | that relates to your submission. You don't want to duplicate effort. |
81 | | - <!-- 1. Please sign our [Contributor License Agreement (CLA)](#cla) before sending PRs. |
82 | | - We cannot accept code without this. --> |
83 | 88 | 1. Fork the nestjs/nest repo. |
84 | 89 | 1. Make your changes in a new git branch: |
85 | 90 |
|
@@ -195,10 +200,11 @@ $ npm run lint |
195 | 200 |
|
196 | 201 | To ensure consistency throughout the source code, keep these rules in mind as you are working: |
197 | 202 |
|
198 | | -* All features or bug fixes **must be tested** by one or more specs (unit-tests). |
199 | | - <!-- |
| 203 | +<!-- |
200 | 204 | // We're working on auto-documentation. |
201 | 205 | * All public API methods **must be documented**. (Details TBC). --> |
| 206 | + |
| 207 | +* All features or bug fixes **must be tested** by one or more specs (unit-tests). |
202 | 208 | * We follow [Google's JavaScript Style Guide][js-style-guide], but wrap all code at |
203 | 209 | **100 characters**. An automated formatter is available, see |
204 | 210 | [DEVELOPER.md](docs/DEVELOPER.md#clang-format). |
@@ -272,8 +278,8 @@ There are currently a few exceptions to the "use package name" rule: |
272 | 278 | * **packaging**: used for changes that change the npm package layout in all of our packages, e.g. public path changes, package.json changes done to all packages, d.ts file/format changes, changes to bundles, etc. |
273 | 279 | * **changelog**: used for updating the release notes in CHANGELOG.md |
274 | 280 | * **sample/#**: for the example apps directory, replacing # with the example app number |
275 | | - <!-- * **aio**: used for docs-app (angular.io) related changes within the /aio directory of the repo --> |
276 | 281 | * none/empty string: useful for `style`, `test` and `refactor` changes that are done across all packages (e.g. `style: add missing semicolons`) |
| 282 | +<!-- * **aio**: used for docs-app (angular.io) related changes within the /aio directory of the repo --> |
277 | 283 |
|
278 | 284 | ### Subject |
279 | 285 |
|
|
0 commit comments