|
| 1 | +# Contributing to hono-routing-controller |
| 2 | + |
| 3 | +We are excited that you're interested in contributing to the `hono-routing-controller` project! This guide will help you get started with contributing to the project. Whether you're submitting a bug fix, a new feature, or an improvement, we appreciate your help! |
| 4 | + |
| 5 | +## Table of Contents |
| 6 | + |
| 7 | +- [How to Contribute](#how-to-contribute) |
| 8 | +- [Code of Conduct](#code-of-conduct) |
| 9 | +- [Issue Reporting](#issue-reporting) |
| 10 | +- [Pull Request Process](#pull-request-process) |
| 11 | +- [Development Setup](#development-setup) |
| 12 | + |
| 13 | +## How to Contribute |
| 14 | + |
| 15 | +We welcome contributions from the community! To contribute, follow these steps: |
| 16 | + |
| 17 | +1. **Fork the Repository** |
| 18 | + |
| 19 | + First, fork the repository by clicking the "Fork" button at the top right of the repo page. |
| 20 | + |
| 21 | +2. **Clone Your Fork** |
| 22 | + |
| 23 | + Clone your fork to your local machine: |
| 24 | + ```bash |
| 25 | + git clone https://github.com/hasib-devs/hono-routing-controller.git |
| 26 | + cd hono-routing-controller |
| 27 | + ``` |
| 28 | +3. **Create a New Branch** |
| 29 | + |
| 30 | + Always create a new branch for your feature or fix: |
| 31 | + ``` |
| 32 | + git checkout -b feat/your-feature-name |
| 33 | + ``` |
| 34 | +
|
| 35 | + always use semantic branch name. |
| 36 | + - feat |
| 37 | + - fix |
| 38 | + - docs |
| 39 | + - style |
| 40 | + - refactor |
| 41 | + - perf |
| 42 | + - test |
| 43 | + - build |
| 44 | + - ci |
| 45 | + - chore |
| 46 | + - revert |
| 47 | + - merge |
| 48 | +
|
| 49 | +4. **Commit Your Changes** |
| 50 | +
|
| 51 | + Write clear and concise commit messages: |
| 52 | + ```bash |
| 53 | + git commit -m "Add feature/bugfix description" |
| 54 | + ``` |
| 55 | +5. **Push to Your Fork** |
| 56 | + |
| 57 | + Push your changes to your fork: |
| 58 | + ```bash |
| 59 | + git push origin feature/your-feature-name |
| 60 | + ``` |
| 61 | + |
| 62 | +6. **Create a Pull Request** |
| 63 | + |
| 64 | + After pushing your changes, go to the original repository and create a pull request (PR) from your fork. |
| 65 | + |
| 66 | +## Code of Conduct |
| 67 | +We follow a Code of Conduct in this project. By participating, you are expected to honor the code of conduct and engage with the community respectfully. |
| 68 | + |
| 69 | +## Issue Reporting |
| 70 | +If you encounter a bug or have an idea for a new feature, feel free to open an issue. Please include: |
| 71 | + |
| 72 | +A clear description of the problem or feature request. |
| 73 | +Steps to reproduce the issue, if applicable. |
| 74 | +Any relevant log or error messages. |
| 75 | +Information about your environment (e.g., Node.js version, operating system). |
| 76 | + |
| 77 | +## Pull Request Process |
| 78 | +We use the following steps for accepting pull requests: |
| 79 | + |
| 80 | +1. **Ensure Tests Pass** |
| 81 | + |
| 82 | + All tests must pass before we can merge your PR. |
| 83 | + |
| 84 | +2. **Code Review** |
| 85 | + |
| 86 | + Once you submit your PR, a maintainer will review it and may suggest changes. |
| 87 | + |
| 88 | +3. **Merge** |
| 89 | + |
| 90 | + Once your PR is approved, it will be merged into the main branch. |
| 91 | + |
| 92 | +**Please ensure your PR follows these guidelines:** |
| 93 | + |
| 94 | +- Write clear and concise commit messages. |
| 95 | +- Keep the changes focused on a single issue or feature. |
| 96 | +- If adding new features, consider writing tests to cover them. |
| 97 | +- Ensure that existing functionality and tests remain unaffected. |
| 98 | + |
| 99 | +## Development Setup |
| 100 | +To set up your local environment for development: |
| 101 | + |
| 102 | +1. **Clone the Repository** |
| 103 | + |
| 104 | + ```bash |
| 105 | + git clone https://github.com/hasib-devs/hono-routing-controller.git |
| 106 | + ``` |
| 107 | + |
| 108 | +2. **Install Dependencies** |
| 109 | + |
| 110 | + Install the required dependencies: |
| 111 | + ```bash |
| 112 | + pnpm install |
| 113 | + ``` |
| 114 | + |
| 115 | +3. **Start Development** |
| 116 | + |
| 117 | + To run the application locally during development: |
| 118 | + ```bash |
| 119 | + pnpm dev |
| 120 | + ``` |
| 121 | + |
| 122 | +4. **Build** |
| 123 | + |
| 124 | + To create a production build of the application: |
| 125 | + ```bash |
| 126 | + pnpm build |
| 127 | + ``` |
| 128 | + |
| 129 | +5. **Run Tests** |
| 130 | + |
| 131 | + To run the test suite and ensure everything is working: |
| 132 | + ```bash |
| 133 | + pnpm test |
| 134 | + ``` |
| 135 | +___ |
| 136 | +Thanks for your contributions to the hono-routing-controller project! |
| 137 | +___ |
0 commit comments