# Contributing ## Reporting Issues If you have found what you think is a bug, please [file an issue](https://github.com/toss/h6s/issues/new) `Bug_Report` type. ## Suggesting new features If you are here to suggest a feature, first create an issue `Suggestion` type if it does not already exist. ## Development If you have been assigned to fix an issue or develop a new feature, please follow these steps to get started: - Fork this repository - Install dependencies by running `$ yarn` - Implement your changes and tests to files in the `packages/{package}` directory and corresponding test files - To run Storybook. - Document your changes in the appropriate doc page - Git stage your required changes and commit (see below commit guidelines) - also need to run `yarn changeset` - Submit PR for review ## Commit message conventions `h6s` is using [Angular Commit Message Conventions](https://github.com/angular/angular.js/blob/master/DEVELOPERS.md#-git-commit-guidelines). We have very precise rules over how our git commit messages can be formatted. This leads to **more readable messages** that are easy to follow when looking through the **project history**. ### Commit Message Format Each commit message consists of a **header**, a **body** and a **footer**. The header has a special format that includes a **type**, a **scope** and a **subject**: ``` ():