doc(contrib): move cargo fmt notes to CODE_STYLE.md

CONTRIBUTING.md

@@ -8,22 +8,3 @@ You want to contribute? You're awesome! Don't know where to start? Check the [li
 
 - [Submitting a Pull Request](./docs/PULL_REQUESTS.md#submitting-a-pull-request)
 - [Commit Guidelines](./docs/COMMITS.md)
-
-## Cargo fmt
-
-`cargo fmt --all` does not work in hyper. Please use the following commands:
-
-```txt
-# Mac or Linux
-rustfmt --check --edition 2018 $(git ls-files '*.rs')
-
-# Powershell
-Get-ChildItem . -Filter "*.rs" -Recurse | foreach { rustfmt --check --edition 2018 $_.FullName }
-```
-
-> **NOTE**: If you are using `rust-analyzer`, you can add the following two lines in your `settings.json` to make sure the features get taken into account when checking the project:
->
->    ```json
->     "rust-analyzer.cargo.features": ["full"],
->     "rust-analyzer.check.features": ["full"],
->    ```

docs/CODE_STYLE.md

@@ -0,0 +1,22 @@
+# Code Style
+
+hyper uses the default configuration of `rustfmt`.
+
+## cargo fmt
+
+`cargo fmt --all` does not work in hyper. Please use the following commands:
+
+```txt
+# Mac or Linux
+rustfmt --check --edition 2018 $(git ls-files '*.rs')
+
+# Powershell
+Get-ChildItem . -Filter "*.rs" -Recurse | foreach { rustfmt --check --edition 2018 $_.FullName }
+```
+
+> **NOTE**: If you are using `rust-analyzer`, you can add the following two lines in your `settings.json` to make sure the features get taken into account when checking the project:
+>
+>    ```json
+>     "rust-analyzer.cargo.features": ["full"],
+>     "rust-analyzer.check.features": ["full"],
+>    ```