-
Notifications
You must be signed in to change notification settings - Fork 42
How to Contribute
Natalie Pina edited this page Mar 8, 2023
·
4 revisions
We're thrilled to be an open-source project and we can't wait to see you what you contribute!
Please review the contributing documentation beforehand for more details on contributing to the project.
- Fork the repository.
- Clone it to your local system. Be sure to run
npm install
. Then run,npm run storybook
to start up the app for local development. See more information in our Getting Started Guide. - Create a new branch. We generally follow standards to name our branch like so
<name>/<commit type>/<description>
. For example,npina/feat/new-color-picker-component
. - Create your awesome changes. ✨
- Before committing your changes there are several checks you should run to ensure quality work. Test for any linting or type errors by running
npm run lint && npm run test:types
. Make sure that tests are still passing by runningnpm run test
To update snapshot tests, runnpm run test -- -u
and include the updated tests in your commit. - Commit your changes. When committing prefix your commit message with the appropriate conventional commit type. For example,
fix: <insert what was fixed>
. To choose the appropriate commit type for your changes, please review the list of Commit Types. - Push up your changes. In GitHub, click the compare & pull request button to begin drafting your pull request.
- Fill out the pull request form, and it will be reviewed shortly by the UI Team.
Please let us know if you have any issues with the steps outlined above!