# Contributing

## How to Contribute to Brise Chain Documentations Project <a href="#how-to-contribute-to-brise-chain-documentations-project" id="how-to-contribute-to-brise-chain-documentations-project"></a>

Your contributions to the [Brise Chain](https://www.brisescan.com/) will help build a fast and secure decentralized digital asset exchange.

We want to make it as easy as possible to contribute changes that help the Brise Chain grow and thrive. There are a few guidelines that we ask contributors to follow so that we can merge your changes quickly.

### Getting Started <a href="#getting-started" id="getting-started"></a>

* Make sure you have a [GitHub account](https://github.com/signup/free).
* Create a GitHub issue for your contribution, assuming one does not already exist.
* Clearly describe the issue including steps to reproduce if it is a bug.
* Fork the repository on GitHub.

#### Minor Changes <a href="#minor-changes" id="minor-changes"></a>

**Documentation**

For small changes to comments and documentation, it is not always necessary to create a new GitHub issue. In this case, it is appropriate to start the first line of a commit with 'doc' instead of an issue number.

### Finding things to work on <a href="#finding-things-to-work-on" id="finding-things-to-work-on"></a>

The first place to start is always looking over the current GitHub issues for the project you are interested in contributing to. Issues marked with \[help wanted]\[help-wanted] are usually pretty self-contained and a good place to get started.

Of course, feel free to create a new issue if you think something needs to be added or fixed.

### Making Changes <a href="#making-changes" id="making-changes"></a>

* Create a topic branch from where you want to base your work.
* This is usually the master branch.
* Please avoid working directly on the `master` branch.
* Make sure you have added the necessary tests for your changes and make sure all tests pass.

<br>