Skip to content

Commit 2c44eba

Browse files
CONTRIBUTING.md: Remove trailing whitespaces (pytorch#7857)
Co-authored-by: Nicolas Hug <nh.nicolas.hug@gmail.com>
1 parent 965bcab commit 2c44eba

File tree

1 file changed

+15
-15
lines changed

1 file changed

+15
-15
lines changed

CONTRIBUTING.md

+15-15
Original file line numberDiff line numberDiff line change
@@ -4,22 +4,22 @@ We want to make contributing to this project as easy and transparent as possible
44

55
## TL;DR
66

7-
We appreciate all contributions. If you are interested in contributing to Torchvision, there are many ways to help out.
7+
We appreciate all contributions. If you are interested in contributing to Torchvision, there are many ways to help out.
88
Your contributions may fall into the following categories:
99

10-
- It helps the project if you could
10+
- It helps the project if you could
1111
- Report issues you're facing
12-
- Give a :+1: on issues that others reported and that are relevant to you
12+
- Give a :+1: on issues that others reported and that are relevant to you
1313

1414
- Answering queries on the issue tracker, investigating bugs are very valuable contributions to the project.
1515

16-
- You would like to improve the documentation. This is no less important than improving the library itself!
16+
- You would like to improve the documentation. This is no less important than improving the library itself!
1717
If you find a typo in the documentation, do not hesitate to submit a GitHub pull request.
1818

1919
- If you would like to fix a bug
2020
- please pick one from the [list of open issues labelled as "help wanted"](https://github.com/pytorch/vision/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22)
2121
- comment on the issue that you want to work on this issue
22-
- send a PR with your fix, see below.
22+
- send a PR with your fix, see below.
2323

2424
- If you plan to contribute new features, utility functions or extensions, please first open an issue and discuss the feature with us.
2525

@@ -85,12 +85,12 @@ If you plan to modify the code or documentation, please follow the steps below:
8585
4. Ensure the test suite passes.
8686
5. Make sure your code passes the formatting checks (see below).
8787

88-
For more details about pull requests,
89-
please read [GitHub's guides](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request).
88+
For more details about pull requests,
89+
please read [GitHub's guides](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request).
9090

9191
If you would like to contribute a new model, please see [here](#New-architecture-or-improved-model-weights).
9292

93-
If you would like to contribute a new dataset, please see [here](#New-dataset).
93+
If you would like to contribute a new dataset, please see [here](#New-dataset).
9494

9595
### Code formatting and typing
9696

@@ -145,8 +145,8 @@ mypy --config-file mypy.ini
145145

146146
### Unit tests
147147

148-
If you have modified the code by adding a new feature or a bug-fix, please add unit tests for that. To run a specific
149-
test:
148+
If you have modified the code by adding a new feature or a bug-fix, please add unit tests for that. To run a specific
149+
test:
150150
```bash
151151
pytest test/<test-module.py> -vvv -k <test_myfunc>
152152
# e.g. pytest test/test_transforms.py -vvv -k test_center_crop
@@ -155,7 +155,7 @@ pytest test/<test-module.py> -vvv -k <test_myfunc>
155155
If you would like to run all tests:
156156
```bash
157157
pytest test -vvv
158-
```
158+
```
159159

160160
Tests that require internet access should be in
161161
`test/test_internet.py`.
@@ -208,18 +208,18 @@ with "transforms" in their name.
208208
### New architecture or improved model weights
209209

210210
Please refer to the guidelines in [Contributing to Torchvision - Models](https://github.com/pytorch/vision/blob/main/CONTRIBUTING_MODELS.md).
211-
211+
212212
### New dataset
213213

214-
Please, do not send any PR with a new dataset without discussing
214+
Please, do not send any PR with a new dataset without discussing
215215
it in an issue as, most likely, it will not be accepted.
216216

217217
### Pull Request
218218

219-
If all previous checks (flake8, mypy, unit tests) are passing, please send a PR. Submitted PR will pass other tests on
219+
If all previous checks (flake8, mypy, unit tests) are passing, please send a PR. Submitted PR will pass other tests on
220220
different operating systems, python versions and hardware.
221221

222-
For more details about pull requests workflow,
222+
For more details about pull requests workflow,
223223
please read [GitHub's guides](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request).
224224

225225
## License

0 commit comments

Comments
 (0)