|
| 1 | +# Contributing to Distribution Plot Logger |
| 2 | + |
| 3 | +Thank you for your interest in contributing to **Distribution Plot Logger**! Your contributions help improve this project and benefit the community. Below are guidelines to help you contribute effectively. |
| 4 | + |
| 5 | +## Table of Contents |
| 6 | + |
| 7 | +- [How to Contribute](#how-to-contribute) |
| 8 | +- [Bug Reports](#bug-reports) |
| 9 | +- [Feature Requests](#feature-requests) |
| 10 | +- [Pull Requests](#pull-requests) |
| 11 | +- [Coding Guidelines](#coding-guidelines) |
| 12 | +- [Commit Messages](#commit-messages) |
| 13 | +- [Testing](#testing) |
| 14 | +- [Documentation](#documentation) |
| 15 | +- [License](#license) |
| 16 | + |
| 17 | +## How to Contribute |
| 18 | + |
| 19 | +1. **Fork the Repository:** |
| 20 | + Fork the project on GitHub. |
| 21 | + |
| 22 | +2. **Clone Your Fork:** |
| 23 | + |
| 24 | + ```bash |
| 25 | + git clone https://github.com/Afitzy98/dist-plot-log.git |
| 26 | + cd distribution-plot-logger |
| 27 | + ``` |
| 28 | + |
| 29 | +3. **Create a Branch for Your Feature or Bugfix:** |
| 30 | + Use a descriptive branch name, for example: |
| 31 | + |
| 32 | + ```bash |
| 33 | + git checkout -b feature/new-awesome-feature |
| 34 | + ``` |
| 35 | + |
| 36 | + or |
| 37 | + |
| 38 | + ```bash |
| 39 | + git checkout -b bugfix/fix-plot-issue |
| 40 | + ``` |
| 41 | + |
| 42 | +4. **Install Dependencies:** |
| 43 | + Run the following command to install all required packages: |
| 44 | + |
| 45 | + ```bash |
| 46 | + yarn |
| 47 | + ``` |
| 48 | + |
| 49 | +5. **Implement Your Changes:** |
| 50 | + Make your changes or add new features. Please ensure you follow the coding guidelines listed below and write tests for new functionality. |
| 51 | + |
| 52 | +6. **Run Tests and Linting:** |
| 53 | + Run the test suite to ensure everything is working: |
| 54 | + |
| 55 | + ```bash |
| 56 | + yarn test |
| 57 | + ``` |
| 58 | + |
| 59 | + Also, check the code style and linting (if applicable). |
| 60 | + |
| 61 | +7. **Commit Your Changes:** |
| 62 | + We use [Commitizen](https://github.com/commitizen/cz-conventional-changelog) to ensure our commit messages follow the Conventional Commits standard. Instead of using `git commit`, run: |
| 63 | + |
| 64 | + ```bash |
| 65 | + yarn commit |
| 66 | + ``` |
| 67 | + |
| 68 | + This will prompt you to create a well-structured commit message. |
| 69 | + |
| 70 | +8. **Push Your Branch and Create a Pull Request:** |
| 71 | + Push your branch: |
| 72 | + ```bash |
| 73 | + git push origin feature/new-awesome-feature |
| 74 | + ``` |
| 75 | + Then, go to GitHub and create a Pull Request (PR) from your branch. Please include a detailed description of your changes and reference any related issues. |
| 76 | + |
| 77 | +## Bug Reports |
| 78 | + |
| 79 | +If you encounter a bug, please: |
| 80 | + |
| 81 | +- Search existing issues to see if it has already been reported. |
| 82 | +- Open a new issue with a clear and descriptive title. |
| 83 | +- Provide detailed steps to reproduce the bug, expected behavior, and any relevant logs or screenshots. |
| 84 | + |
| 85 | +## Feature Requests |
| 86 | + |
| 87 | +For new features or improvements: |
| 88 | + |
| 89 | +- Please open an issue to discuss your suggestion before starting work. |
| 90 | +- Once discussed, you are welcome to implement the feature and submit a pull request. |
| 91 | + |
| 92 | +## Pull Requests |
| 93 | + |
| 94 | +When submitting a Pull Request: |
| 95 | + |
| 96 | +- Ensure your branch is up to date with the latest `main` branch changes. |
| 97 | +- Confirm that all tests pass by running `yarn test`. |
| 98 | +- Update documentation as needed. |
| 99 | +- Make sure your commit messages follow the Conventional Commits standard (see the [Commit Messages](#commit-messages) section below). |
| 100 | + |
| 101 | +## Coding Guidelines |
| 102 | + |
| 103 | +- **Language:** Please use TypeScript for all code. |
| 104 | +- **Code Style:** Follow the existing code style. Consistency is key. |
| 105 | +- **Testing:** Write tests for new features and bug fixes using Jest. |
| 106 | +- **Documentation:** Update the README and add comments where necessary to help explain your changes. |
| 107 | + |
| 108 | +## Commit Messages |
| 109 | + |
| 110 | +We follow the [Conventional Commits](https://www.conventionalcommits.org/) standard. A commit message should have the following format: |
| 111 | + |
| 112 | +``` |
| 113 | +<type>(<scope>): <subject> |
| 114 | +
|
| 115 | +<body> |
| 116 | +``` |
| 117 | + |
| 118 | +**Examples:** |
| 119 | + |
| 120 | +- `fix(parser): correct parsing of numbers` |
| 121 | +- `feat(ui): add new chart color option` |
| 122 | +- `docs(readme): update installation instructions` |
| 123 | + |
| 124 | +## Testing |
| 125 | + |
| 126 | +Our test suite is built using Jest. To run tests, execute: |
| 127 | + |
| 128 | +```bash |
| 129 | +yarn test |
| 130 | +``` |
| 131 | + |
| 132 | +Please add tests for any new functionality or bug fixes you introduce. |
| 133 | + |
| 134 | +## Documentation |
| 135 | + |
| 136 | +Keep documentation up to date. If you modify code functionality or introduce new features, update the README and inline comments accordingly. |
| 137 | + |
| 138 | +## License |
| 139 | + |
| 140 | +By contributing, you agree that your contributions will be licensed under the project's [MIT License](LICENSE). |
| 141 | + |
| 142 | +--- |
| 143 | + |
| 144 | +Thank you for contributing to **Distribution Plot Logger**! |
0 commit comments