8e2fff84c72ce2b4605fd89c002114fb113d3dfd83574fa82ae963d8bb372522622c1f3ed4c7142827a18d1ae8f9655fa5fbe748fb54134b690c8c2f5a844d 1.6 KB

1234567891011121314151617
  1. # Contributing to Handsontable
  2. Your contributions to this project are very welcome. If you want to fix a bug or propose a new feature, you can open a new Pull Request but first make sure it follows these general rules:
  3. 1. Sign this [Contributor License Agreement](https://goo.gl/forms/yuutGuN0RjsikVpM2) to allow us to publish your changes to the code.
  4. 2. Make your changes on a separate branch. This will speed up the merging process.
  5. 3. Always make the target of your pull request the `develop` branch, not `master`.
  6. 4. Do not edit files in `dist/` directory (e.g: `handsontable.js`, `handsontable.css`, `handsontable.full.js`, `handsontable.full.css`). Instead, edit files inside the `src/` directory and then use `npm run build` to make a build. More information about this you can find [here](https://docs.handsontable.com/tutorial-custom-build.html).
  7. 5. **Important: For any change you make, please add at least one test case** in `test/e2e/` (for End-to-End tests), `test/unit/` or `src/3rdparty/walkontable/test/spec/`. That will help us understand the issue and make sure that it stays fixed forever. Read more about our [testing process](http://docs.handsontable.com/tutorial-testing.html).
  8. 6. Please review our [coding style](https://github.com/handsontable/handsontable/wiki/Coding-style) for instructions on how to properly style the code.
  9. 7. Add a thorough description of all the changes.
  10. Thank you for your commitment!
  11. ## Team rules
  12. The Handsontable team utilizes Git-Flow. Read more - [How we use Git-Flow](https://github.com/handsontable/handsontable/wiki/How-we-use-Git-Flow)