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
+22-5
Original file line number
Diff line number
Diff line change
@@ -32,20 +32,33 @@ Here's how to get started with your code contribution:
32
32
33
33
1. Create your own fork of go-redis
34
34
2. Do the changes in your fork
35
-
3. If you need a development environment, run `make test`. Note: this clones and builds the latest release of [redis](https://redis.io). You also need a redis-stack-server docker, in order to run the capabilities tests. This can be started by running:
36
-
```docker run -p 6379:6379 -it redis/redis-stack-server:edge```
37
-
4. While developing, make sure the tests pass by running `make tests`
35
+
3. If you need a development environment, run `make docker.start`.
36
+
37
+
> Note: this clones and builds the docker containers specified in `docker-compose.yml`, to understand more about
38
+
> the infrastructure that will be started you can check the `docker-compose.yml`. You also have the possiblity
39
+
> to specify the redis image that will be pulled with the env variable `CLIENT_LIBS_TEST_IMAGE`.
40
+
> By default the docker image that will be pulled and started is `redislabs/client-libs-test:rs-7.4.0-v2`.
41
+
> If you want to test with newer Redis version, using a newer version of `redislabs/client-libs-test` should work out of the box.
42
+
43
+
4. While developing, make sure the tests pass by running `make test` (if you have the docker containers running, `make test.ci` may be sufficient).
44
+
> Note: `make test` will try to start all containers, run the tests with `make test.ci` and then stop all containers.
38
45
5. If you like the change and think the project could use it, send a
39
46
pull request
40
47
41
48
To see what else is part of the automation, run `invoke -l`
42
49
50
+
43
51
## Testing
44
52
45
-
Call `make test` to run all tests, including linters.
53
+
### Setting up Docker
54
+
To run the tests, you need to have Docker installed and running. If you are using a host OS that does not support
55
+
docker host networks out of the box (e.g. Windows, OSX), you need to set up a docker desktop and enable docker host networks.
56
+
57
+
### Running tests
58
+
Call `make test` to run all tests.
46
59
47
60
Continuous Integration uses these same wrappers to run all of these
48
-
tests against multiple versions of python. Feel free to test your
61
+
tests against multiple versions of redis. Feel free to test your
49
62
changes against all the go versions supported, as declared by the
50
63
[build.yml](./.github/workflows/build.yml) file.
51
64
@@ -99,3 +112,7 @@ The core team regularly looks at pull requests. We will provide
99
112
feedback as soon as possible. After receiving our feedback, please respond
100
113
within two weeks. After that time, we may close your PR if it isn't
101
114
showing any activity.
115
+
116
+
## Support
117
+
118
+
Maintainers can provide limited support to contributors on discord: https://discord.gg/W4txy5AeKM
0 commit comments