@@ -48,14 +48,16 @@ contributions, and don't want a wall of rules to get in the way of that.
48
48
49
49
That said, if you want to ensure that a pull request is likely to be merged,
50
50
talk to us! You can find out our thoughts and ensure that your contribution
51
- won't clash or be obviated by ORY Dockertest's normal direction. A great way to
52
- do this is via the [ ORY Community] ( https://community.ory.sh/ ) or join the
53
- [ ORY Chat] ( https://www.ory.sh/chat ) .
51
+ won't clash or be obviated by ORY
52
+ Dockertest's normal direction. A great way to
53
+ do this is via
54
+ [ ORY Dockertest Discussions] ( https://github.com/ory/dockertest/discussions )
55
+ or the [ ORY Chat] ( https://www.ory.sh/chat ) .
54
56
55
57
## FAQ
56
58
57
59
- I am new to the community. Where can I find the
58
- [ ORY Community Code of Conduct?] ( https://github.com/ory/Dockertest /blob/master/CODE_OF_CONDUCT.md )
60
+ [ ORY Community Code of Conduct?] ( https://github.com/ory/dockertest /blob/master/CODE_OF_CONDUCT.md )
59
61
60
62
- I have a question. Where can I get
61
63
[ answers to questions regarding ORY Dockertest?] ( #communication )
@@ -77,14 +79,14 @@ do this is via the [ORY Community](https://community.ory.sh/) or join the
77
79
## How can I contribute?
78
80
79
81
If you want to start contributing code right away, we have a
80
- [ list of good first issues] ( https://github.com/ory/Dockertest /labels/good%20first%20issue ) .
82
+ [ list of good first issues] ( https://github.com/ory/dockertest /labels/good%20first%20issue ) .
81
83
82
84
There are many other ways you can contribute without writing any code. Here are
83
85
a few things you can do to help out:
84
86
85
87
- ** Give us a star.** It may not seem like much, but it really makes a
86
- difference. This is something that everyone can do to help out ORY
87
- Dockertest. Github stars help the project gain visibility and stand out.
88
+ difference. This is something that everyone can do to help out ORY Dockertest.
89
+ Github stars help the project gain visibility and stand out.
88
90
89
91
- ** Join the community.** Sometimes helping people can be as easy as listening
90
92
to their problems and offering a different perspective. Join our Slack, have a
@@ -110,8 +112,10 @@ a few things you can do to help out:
110
112
We use [ Slack] ( https://www.ory.sh/chat ) . You are welcome to drop in and ask
111
113
questions, discuss bugs and feature requests, talk to other users of ORY, etc.
112
114
113
- We have a [ forum] ( https://community.ory.sh/ ) . This is a great place for in-depth
114
- discussions and lots of code examples, logs and similar data.
115
+ Check out
116
+ [ ORY Dockertest Discussions] ( https://github.com/ory/dockertest/discussions ) . This
117
+ is a great place for in-depth discussions and lots of code examples, logs and
118
+ similar data.
115
119
116
120
You can also join our community hangout, if you want to speak to the ORY team
117
121
directly or ask some questions. You can find more info on the hangouts in
@@ -158,11 +162,11 @@ should be merged by the submitter after review.
158
162
159
163
Please provide documentation when changing, removing, or adding features.
160
164
Documentation resides in the project's
161
- [ docs] ( https://github.com/ory/Dockertest /tree/master/docs ) folder. Generate API
165
+ [ docs] ( https://github.com/ory/dockertest /tree/master/docs ) folder. Generate API
162
166
and configuration reference documentation using ` cd docs; npm run gen ` .
163
167
164
168
For further instructions please head over to
165
- [ docs/README.md] ( https://github.com/ory/Dockertest /blob/master/README.md ) .
169
+ [ docs/README.md] ( https://github.com/ory/dockertest /blob/master/README.md ) .
166
170
167
171
## Disclosing vulnerabilities
168
172
0 commit comments