Skip to content

Commit 1b7422d

Browse files
authored
Remove trailing spaces from CONTRIBUTING.md (#9024)
1 parent 50d352f commit 1b7422d

File tree

1 file changed

+20
-20
lines changed

1 file changed

+20
-20
lines changed

CONTRIBUTING.md

Lines changed: 20 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -1,27 +1,27 @@
11
# Contribute To PyTorch/XLA
22

3-
We appreciate all contributions. If you are planning to contribute a bug fix for
3+
We appreciate all contributions. If you are planning to contribute a bug fix for
44
an open issue, please comment on the thread and we're happy to provide guidance.
5-
You are welcome to pick issues with [good first issue](https://github.com/pytorch/xla/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22)
6-
and [help wanted](https://github.com/pytorch/xla/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22)
5+
You are welcome to pick issues with [good first issue](https://github.com/pytorch/xla/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22)
6+
and [help wanted](https://github.com/pytorch/xla/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22)
77
labels to get started.
88

9-
If you plan to contribute new features or extensions to this repository, first
10-
open an issue and discuss the feature with us. Sending a PR without discussion
11-
might result in a rejected PR, because we might be taking the repository in a
9+
If you plan to contribute new features or extensions to this repository, first
10+
open an issue and discuss the feature with us. Sending a PR without discussion
11+
might result in a rejected PR, because we might be taking the repository in a
1212
different direction.
1313

1414
## Building from source
1515

16-
We recommend you use our prebuilt Docker image to start your development work
16+
We recommend you use our prebuilt Docker image to start your development work
1717
using either VS Code or a local container:
1818

1919
### Visual Studio Code Dev Container
2020

21-
* Create an empty directory for your workspace on your development host. These
22-
instructions assume you are using a remote host and are connecting to it over
21+
* Create an empty directory for your workspace on your development host. These
22+
instructions assume you are using a remote host and are connecting to it over
2323
SSH.
24-
24+
2525
* Clone PyTorch, TorchVision, and PyTorch/XLA into your workspace directory:
2626

2727
```bash
@@ -51,17 +51,17 @@ using either VS Code or a local container:
5151
[`Dev Containers`](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers)
5252
extensions.
5353

54-
* From VS Code, connect to your remote host and open your workspace directory.
55-
You will be prompted to reopen your workspace in container. Choose the
56-
appropriate container. Use `tpu-contributor` if you are unsure of which to use.
57-
If you are not prompted to reopen in a container, in the VS Code command
58-
pallete, type `Dev Containers: Reopen in Container` to open your workspace in
59-
one of our pre-built Docker containers. Select the correct container based on
54+
* From VS Code, connect to your remote host and open your workspace directory.
55+
You will be prompted to reopen your workspace in container. Choose the
56+
appropriate container. Use `tpu-contributor` if you are unsure of which to use.
57+
If you are not prompted to reopen in a container, in the VS Code command
58+
pallete, type `Dev Containers: Reopen in Container` to open your workspace in
59+
one of our pre-built Docker containers. Select the correct container based on
6060
your local accelerator. If you're a Googler, you should use the `tpu-internal`
6161
container, which is set up for [bazel remote build caching](https://github.com/pytorch/xla/blob/master/docs/source/contribute/bazel.md#remote-caching)
6262
for faster builds.
6363

64-
* Open a new terminal window in VS Code. Since you are running as root in this
64+
* Open a new terminal window in VS Code. Since you are running as root in this
6565
container, mark the repository directories as safe. The commands below assume
6666
your workspace directory is `torch`, update the commands to use your workspace
6767
directory.
@@ -71,7 +71,7 @@ using either VS Code or a local container:
7171
git config --global --add safe.directory /workspaces/torch/pytorch/xla
7272
git config --global --add safe.directory /workspaces/torch/vision
7373
```
74-
* In the terminal window, run the following commands to build PyTorch,
74+
* In the terminal window, run the following commands to build PyTorch,
7575
TorchVision, and PyTorch/XLA:
7676

7777
```bash
@@ -89,15 +89,15 @@ using either VS Code or a local container:
8989
-f https://storage.googleapis.com/libtpu-releases/index.html
9090
```
9191

92-
* If you are running on a TPU VM, ensure `torch` and `torch_xla` were built and
92+
* If you are running on a TPU VM, ensure `torch` and `torch_xla` were built and
9393
installed correctly:
9494

9595
```bash
9696
python -c 'import torch_xla as xla; print(xla.device())'
9797
# Output: xla:0
9898
```
9999

100-
**Subsequent builds**: after building the packages from source code for the
100+
**Subsequent builds**: after building the packages from source code for the
101101
first time, you may need to build everything again, for example, after a
102102
`git pull`. You can run `scripts/build_developer.sh` which will rebuild PyTorch,
103103
TorchVision, and PyTorch/XLA.

0 commit comments

Comments
 (0)