Thank you for investing your time in contributing to this project!
In this guide you will get an overview of the contribution workflow.
If you spot a problem, search if an issue already exists. If a related issue doesn't exist, you can open a new issue using a relevant issue form.
Scan through existing issues to find one that interests you. You can narrow down the search using labels as filters. If you find an unassigned issue to work on, you are welcome to open a PR with a fix.
Changes should be committed in accordance with the Conventional Commits specification.
- Make sure to link any issues solved by the PR.
- Enable the checkbox to allow maintainer edits so the branch can be updated for a merge. Once you submit your PR, a Docs team member will review your proposal. We may ask questions or request additional information.
- We may ask for changes to be made before a PR can be merged, either using suggested changes or pull request comments. You can apply suggested changes directly through the UI. You can make any other changes in your fork, then commit them to your branch.
- As you update your PR and apply changes, mark each conversation as resolved.
Changesets is used for release management.
While you are free to include accompanying changesets for your PRs, it is not mandatory. Publishing new releases is done by code owners.