# Contributing Before contributing to this plugin, make sure you read the [contributing guide for Kibana](https://github.com/elastic/kibana/blob/main/CONTRIBUTING.md), as well as the [STYLEGUIDE](https://github.com/elastic/kibana/blob/main/STYLEGUIDE.mdx) and [TYPESCRIPT](https://github.com/elastic/kibana/blob/main/TYPESCRIPT.md) md files.. > Kibana recommends working on a fork of the [elastic/kibana repository](https://github.com/elastic/kibana) (see [here](https://docs.github.com/en/get-started/quickstart/fork-a-repo) to learn about forks). > This plugin uses TypeScript, see Kibana's recommendation here. ## Submitting a Pull Request (PR) Before you submit your PR, consider the following guidelines: 1. Be sure that an issue describes the problem you're fixing, or documents the design for the feature you'd like to add. 2. Make your changes in a new git branch. ``` git checkout -b my-branch main ``` 3. Commit your changes using a descriptive commit message that follows our commit message conventions: ``` git commit -a ``` 4. Push your branch to GitHub: ``` git push origin my-fix-branch ``` 5. In GitHub, create a PR. Note: If changes are suggested, then make the required updates, [rebase](https://hackernoon.com/git-merge-vs-rebase-whats-the-diff-76413c117333) your branch, and force push (this will update your PR): ``` git rebase main -i git push -f ``` ## Commit Message Guidelines > **Note:** These guidelines are **recommended - not mandatory**. ### Commit Message Format Each commit message consists of a **header**, **body**, and **footer**. ```