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
We highly appreciate feedback and contributions from the community! If you'd like to contribute to this project, please make sure to review and follow the guidelines below.
4
+
5
+
## Code of conduct
6
+
7
+
In the interest of fostering an open and welcoming environment, please review and follow our [code of conduct](./CODE_OF_CONDUCT.md).
8
+
9
+
## Code and copy reviews
10
+
11
+
All submissions, including submissions by project members, require review. We
12
+
use GitHub pull requests for this purpose. Consult
13
+
[GitHub Help](https://help.github.com/articles/about-pull-requests/) for more
14
+
information on using pull requests.
15
+
16
+
## Report an issue
17
+
18
+
Report all issues through [GitHub Issues](./issues).
19
+
20
+
## File a feature request
21
+
22
+
File your feature request through [GitHub Issues](./issues).
23
+
24
+
## Create a pull request
25
+
26
+
When making pull requests to the repository, make sure to follow these guidelines for both bug fixes and new features:
27
+
28
+
- Before creating a pull request, file a GitHub Issue so that maintainers and the community can discuss the problem and potential solutions before you spend time on an implementation.
29
+
- In your PR's description, link to any related issues or pull requests to give reviewers the full context of your change.
30
+
- For commit messages, follow the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) format.
31
+
- For example, if you update documentation for a specific extension, your commit message might be: `docs(extension-name) updated installation documentation`.
0 commit comments