Browse code
Remove DCO small patch exception
As we move forward on automating our pull request review process and
tooling these exceptions hurt more than they help. For consistency we
should not allow small patch exceptions for anything. The source of
truth going forward for DCO and builds are the official drone status on
each pull request.
Signed-off-by: Michael Crosby <crosbymichael@gmail.com>
Michael Crosby authored on 2014/11/07 05:03:13Showing 1 changed files
| ... | ... |
@@ -272,18 +272,6 @@ Note that the old-style `Docker-DCO-1.1-Signed-off-by: ...` format is still |
| 272 | 272 |
accepted, so there is no need to update outstanding pull requests to the new |
| 273 | 273 |
format right away, but please do adjust your processes for future contributions. |
| 274 | 274 |
|
| 275 |
-#### Small patch exception |
|
| 276 |
- |
|
| 277 |
-There are several exceptions to the signing requirement. Currently these are: |
|
| 278 |
- |
|
| 279 |
-* Your patch fixes spelling or grammar errors. |
|
| 280 |
-* Your patch is a single line change to documentation contained in the |
|
| 281 |
- `docs` directory. |
|
| 282 |
-* Your patch fixes Markdown formatting or syntax errors in the |
|
| 283 |
- documentation contained in the `docs` directory. |
|
| 284 |
- |
|
| 285 |
-If you have any questions, please refer to the FAQ in the [docs](http://docs.docker.com) |
|
| 286 |
- |
|
| 287 | 275 |
### How can I become a maintainer? |
| 288 | 276 |
|
| 289 | 277 |
* Step 1: Learn the component inside out |