We appreciate your interest in contributing to our project! Below are guidelines on how to help us improve and develop this project further.
-
Fork the repository Click the "Fork" button at the top right of this repository and create your own fork of the project.
-
Create a feature branch Create a new branch for your feature or bugfix:
git checkout -b feature/YourFeatureName
-
Make your changes Make your changes in the source files and ensure that everything works as expected. Please follow the code style and structure used in the project.
-
Commit your changes When your changes are ready, commit them with a clear and descriptive message:
git commit -m "Add YourFeatureName"
-
Push to your branch Push your branch to GitHub:
git push origin feature/YourFeatureName
-
Submit a pull request (PR) Open a pull request to the
main
branch. Ensure you include a description of your changes and why they're needed.
If your pull request is merged into the main
branch and you're ready to release a new version of the project, follow the steps below.
-
After your pull request is merged, run the following command to create a new changeset:
yarn changeset
- Select the type of change (
major
,minor
, orpatch
). - Provide a short description of the changes.
- Select the type of change (
-
This will generate a Markdown file in the
.changeset
directory with the list of changes. -
To finalize the release process, run the following command after the changeset is created:
yarn changeversion
This command will:
- Update the
package.json
version number. - Generate the
CHANGELOG.md
file with the list of changes.
Important: If you do not run
yarn changeversion
, the release will be delayed until this step is completed. - Update the
-
After this step, the next push to the
main
branch will trigger the release process.
- Ensure that your code follows the style and conventions used in the project.
- Add appropriate test coverage for any new features or changes.
- Make sure that the project builds and passes all tests before submitting your PR.
- Update documentation if necessary, especially if your changes introduce new features or modify existing functionality.
Thank you for considering contributing to this project. Your contributions make the open-source community an amazing place to learn, inspire, and create.