You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- In general, contributors should make code changes on a branch, and then [create a pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request) to have the changes merged
3
+
## 1. General guideline
4
+
5
+
In general, contributors should make code changes on a branch, and then [create a pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request) to have the changes merged.
6
+
7
+
## 2. Install the library for development
8
+
4
9
- It is strongly recommended that contributors work on code changes in an isolated Python environment
5
-
+ Use `pip install -e .` to install this library locally, so that any local code changes are reflected immediately in your current Python environment
6
-
- To make sure your code style is compliant, run `./run_linting.sh` locally on your computer to check style violations
10
+
- Use `pip install -e .` to install this library locally, so that any local code changes are reflected immediately in your current Python environment
11
+
12
+
## 3. Running local tests and linting
13
+
14
+
Make sure to run the following checks on your local computer, before pushing any code to GitHub:
15
+
- Code style: run `./run_linting.sh`
7
16
+ You might want to run `chmod +x run_linting.sh` to make `run_linting.sh` executable
8
-
-Please also run all unit tests by running `./run_tests.sh` before committing code to GitHub
17
+
-Unit tests: run `./run_tests.sh`
9
18
+ You might want to run `chmod +x run_tests.sh` to make `run_tests.sh` executable
10
-
- Even if you don't run unit tests and check code styles locally, unit tests and code styles are checked on every push at GitHub
19
+
20
+
(Even if you forget to run the checking above on your local computer, unit tests and code styles are checked on every push at GitHub.)
21
+
22
+
## 4. Update the documentations
23
+
24
+
If you would like to make changes to the documentations of this library, you need to install the dependencies for building documentations with the following command (from the root directory):
25
+
26
+
```
27
+
pip install -r docs/requirements.txt
28
+
```
29
+
30
+
To build the documentation HTML pages locally, navigate to the `docs` folder, and run `make clean html`. To view the generated HTML documentation, open the file `docs/build/html/index.html` in the browser.
0 commit comments