Skip to content

Commit 731868f

Browse files
committed
chore: update repository templates to ory/meta@bc603a6
1 parent f8ba0fa commit 731868f

File tree

1 file changed

+7
-25
lines changed

1 file changed

+7
-25
lines changed

CONTRIBUTING.md

+7-25
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@
1010
- [FAQ](#faq)
1111
- [How can I contribute?](#how-can-i-contribute)
1212
- [Communication](#communication)
13-
- [Contribute examples](#contribute-examples)
13+
- [Contribute examples or community projects](#contribute-examples-or-community-projects)
1414
- [Contribute code](#contribute-code)
1515
- [Contribute documentation](#contribute-documentation)
1616
- [Disclosing vulnerabilities](#disclosing-vulnerabilities)
@@ -123,34 +123,16 @@ projects that you are interested in.
123123

124124
Also, [follow us on Twitter](https://twitter.com/orycorp).
125125

126-
## Contribute examples
126+
## Contribute examples or community projects
127127

128-
One of the most impactful ways to contribute is by adding examples. You can find
129-
an overview of examples using Ory services on the
130-
[documentation examples page](https://www.ory.sh/docs/examples). Source code for
131-
examples can be found in most cases in the
132-
[ory/examples](https://github.com/ory/examples) repository.
128+
One of the most impactful ways to contribute is by adding code examples or other
129+
Ory-related code. You can find an overview of community code in the
130+
[awesome-ory](https://github.com/ory/awesome-ory) repository.
133131

134132
_If you would like to contribute a new example, we would love to hear from you!_
135133

136-
Please [open an issue](https://github.com/ory/examples/issues/new/choose) to
137-
describe your example before you start working on it. We would love to provide
138-
guidance to make for a pleasant contribution experience. Go through this
139-
checklist to contribute an example:
140-
141-
1. Create a GitHub issue proposing a new example and make sure it's different
142-
from an existing one.
143-
1. Fork the repo and create a feature branch off of `master` so that changes do
144-
not get mixed up.
145-
1. Add a descriptive prefix to commits. This ensures a uniform commit history
146-
and helps structure the changelog. Please refer to this
147-
[Convential Commits configuration](https://github.com/ory/keto/blob/master/.github/workflows/conventional_commits.yml)
148-
for the list of accepted prefixes. You can read more about the Conventional
149-
Commit specification
150-
[at their site](https://www.conventionalcommits.org/en/v1.0.0/).
151-
1. Create a `README.md` that explains how to use the example. (Use
152-
[the README template](https://github.com/ory/examples/blob/master/_common/README.md)).
153-
1. Open a pull request and maintainers will review and merge your example.
134+
Please [open a pull request at awesome-ory](https://github.com/ory/awesome-ory/)
135+
to add your example or Ory-related project to the awesome-ory README.
154136

155137
## Contribute code
156138

0 commit comments

Comments
 (0)