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
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@
11
11
This [github document](https://help.github.com/articles/creating-a-pull-request/) provides some guidance on how to create a pull request in github.
12
12
13
13
## PR requirement
14
-
To pursue engineering excellence, we have insisted on the highest stardard on the quality of each PR.
14
+
To pursue engineering excellence, we have insisted on the highest standard for the quality of each PR.
15
15
16
16
* For each PR, please run [golint](https://github.com/golang/lint), [goimports](https://godoc.org/golang.org/x/tools/cmd/goimports), to fix the basic issues/warnings.
17
17
* Make sure you understand [How to Write a Git Commit Message](https://chris.beams.io/posts/git-commit/).
@@ -21,7 +21,7 @@ To pursue engineering excellence, we have insisted on the highest stardard on th
21
21
The best practice is to reorder and squash your local commits before the PR submission to create an atomic and self-contained PR.
22
22
This [book chapter](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History) provides detailed explanation and guidance on how to rewrite the local git history.
23
23
24
-
For exampple, a typical workflow is like the following.
24
+
For example, a typical workflow is like the following.
25
25
```bash
26
26
# assuming you are working on a fix of bug1, and use a local branch called "fixes_of_bug1".
Copy file name to clipboardExpand all lines: README.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -150,7 +150,7 @@ make debug-kill
150
150
151
151
To keep things consistent, we have a docker image to run all tests. **These are the same tests ran on the pull request checks**.
152
152
153
-
Note that all testing docker container binds a couple of ports to the host machine for your convince. The ports are:
153
+
Note that all test Docker containers bind several ports to the host machine for your convenience. The ports are:
154
154
*`9500` - Shard 0 RPC for a validator
155
155
*`9501` - Shard 1 RPC for a validator
156
156
*`9599` - Shard 0 RPC for an explorer
@@ -174,7 +174,7 @@ To run this test, do:
174
174
make test-rpc
175
175
```
176
176
This test starts a localnet (within the Docker container), **ensures it reaches a consensus**, and runs a series of tests to ensure correct RPC behavior.
177
-
This test also acts as a preliminary integration test (more through tests are done on the testnets).
177
+
This test also acts as a preliminary integration test (more thorough tests are done on the testnets).
178
178
> The tests ran by this command can be found [here](https://github.com/harmony-one/harmony-test/tree/master/localnet).
179
179
180
180
If you wish to debug further with the localnet after the tests are done, open a new shell and run:
@@ -194,7 +194,7 @@ To run this test, do:
194
194
make test-rosetta
195
195
```
196
196
This test starts a localnet (within the Docker container), **ensures it reaches a consensus**, and runs the Construction & Data API checks using the [rosetta-cli](https://github.com/coinbase/rosetta-cli).
197
-
This test also acts as a preliminary integration test (more through tests are done on the testnets).
197
+
This test also acts as a preliminary integration test (more thorough tests are done on the testnets).
198
198
> The config for this test can be found [here](https://github.com/harmony-one/harmony-test/blob/master/localnet/configs/localnet_rosetta_test_s0.json) & [here](https://github.com/harmony-one/harmony-test/blob/master/localnet/configs/localnet_rosetta_test_s1.json)
199
199
200
200
Similar to the RPC tests, if you wish to debug further with the localnet after the tests are done, open a new shell and run:
0 commit comments