1## Related issue
2
3<!--
4Please link the GitHub issue this pull request resolves in the format of `#1234`. If you discussed this change
5with a maintainer, please mention her/him using the `@` syntax (e.g. `@aeneasr`).
6
7If this change neither resolves an existing issue nor has sign-off from one of the maintainers, there is a
8chance substantial changes will be requested or that the changes will be rejected.
9
10You can discuss changes with maintainers either in the Github Discusssions in this repository or
11join the [ORY Chat](https://www.ory.sh/chat).
12-->
13
14## Proposed changes
15
16<!--
17Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request.
18-->
19
20## Checklist
21
22<!--
23Put an `x` in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of
24them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.
25-->
26
27- [ ] I have read the [contributing guidelines](../blob/master/CONTRIBUTING.md)
28 and signed the CLA.
29- [ ] I have read the [security policy](../security/policy).
30- [ ] I confirm that this pull request does not address a security
31 vulnerability. If this pull request addresses a security vulnerability, I
32 confirm that I got green light (please contact
33 [security@ory.sh](mailto:security@ory.sh)) from the maintainers to push
34 the changes.
35- [ ] I have added tests that prove my fix is effective or that my feature
36 works.
37- [ ] I have added necessary documentation within the code base (if
38 appropriate).
39
40## Further comments
41
42<!--
43If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution
44you did and what alternatives you considered, etc...
45-->
View as plain text