# Contributing to Apache APISIX Dashboard We would love for you to contribute to Apache APISIX Dashboard and help make it even better than it is today! As a contributor, here are the guidelines we would like you to follow: - [Code of Conduct](#coc) - [How to contribute?](#contribute) - [How to report a bug?](#bug) - [How to add a new feature?](#feature) - [Commit Message Guidelines](#commit) - [Question or Problem?](#question) ## Code of Conduct This project and everyone participating in it is governed by the Apache software Foundation's [Code of Conduct](http://www.apache.org/foundation/policies/conduct.html). By participating, you are expected to adhere to this code. If you are aware of unacceptable behavior, please visit the [Reporting Guidelines page](http://www.apache.org/foundation/policies/conduct.html#reporting-guidelines) and follow the instructions there. ## How to contribute? Most of the contributions that we receive are code contributions, but you can also contribute to the documentation or simply report solid bugs for us to fix. ## How to report a bug? - **Ensure the bug was not already reported** by searching on GitHub under [Issues](https://github.com/apache/apisix-dashboard/issues). - If you're unable to find an open issue addressing the problem, [open a new one](https://github.com/apache/apisix-dashboard/issues/new). Be sure to include a **title and clear description**, as much relevant information as possible, and a **code sample** or an **executable test case** demonstrating the expected behavior that is not occurring. ## How to add a new feature or change an existing one _Before making any significant changes, please [open an issue](https://github.com/apache/apisix-dashboard/issues)._ Discussing your proposed changes ahead of time will make the contribution process smooth for everyone. Once we've discussed your changes and you've got your code ready, make sure that tests are passing and open your pull request. Your PR is most likely to be accepted if it: - Update the README.md with details of changes to the interface. - Includes tests for new functionality. - References the original issue in description, e.g. "resolve #123". - Has a [good commit message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html). ## Commit Message Format *This specification is inspired by and supersedes the [AngularJS commit message format][commit-message-format].* We have very precise rules over how our Git commit messages must be formatted. This format leads to **easier to read commit history**. Each commit message consists of a **header**, a **body**, and a **footer**. ```