Fix .md file style warnings
This commit is contained in:
@@ -71,7 +71,7 @@ Run the project in production with gunicorn. Refer to [this page](https://www.di
|
||||
|
||||
Install production dependencies.
|
||||
|
||||
```
|
||||
```bash
|
||||
pip install -r requirements.production.txt
|
||||
```
|
||||
|
||||
@@ -82,7 +82,8 @@ Do not use `rebase` when pulling or merging changes. Rebasing transforms the com
|
||||
When you start working on a feature, create a feature branch for your changes. These feature branches should be prefixed with `feature`.
|
||||
|
||||
Example of creating a feature branch:
|
||||
```
|
||||
|
||||
```bash
|
||||
git checkout -b feature-error-page
|
||||
```
|
||||
|
||||
@@ -96,13 +97,13 @@ Merge requests to `master` should be reviewed by multiple developers. Only a mod
|
||||
|
||||
Lint python files using `pycodestyle` with
|
||||
|
||||
```
|
||||
```bash
|
||||
pycodestyle --config=setup.cfg --count .
|
||||
```
|
||||
|
||||
Lint javascript and markdown using `eslint` and `remark` with
|
||||
|
||||
```
|
||||
```bash
|
||||
npm test
|
||||
```
|
||||
|
||||
@@ -112,7 +113,7 @@ Use an editor with linting capabilities to write pretty code that passes linting
|
||||
|
||||
Run unit tests with
|
||||
|
||||
```
|
||||
```bash
|
||||
python manage.py test -v 2
|
||||
```
|
||||
|
||||
|
||||
Reference in New Issue
Block a user