|  | 
|  | 1 | +# Contributing to Smelly Test | 
|  | 2 | + | 
|  | 3 | +Thank you for considering contributing to **Smelly Test**! Your contributions make this project better for everyone. This guide will help you set up the project and contribute effectively. | 
|  | 4 | + | 
|  | 5 | +--- | 
|  | 6 | + | 
|  | 7 | +## Getting Started | 
|  | 8 | + | 
|  | 9 | +### Prerequisites | 
|  | 10 | + | 
|  | 11 | +Ensure you have the following installed: | 
|  | 12 | + | 
|  | 13 | +- [Node.js](https://nodejs.org/) (version 18 or higher) | 
|  | 14 | + | 
|  | 15 | +### Setting Up the Project Locally | 
|  | 16 | + | 
|  | 17 | +1. **Fork the Repository**   | 
|  | 18 | +   Click the "Fork" button at the top-right of the repository page to create a copy in your GitHub account. | 
|  | 19 | + | 
|  | 20 | +2. **Clone Your Forked Repository**   | 
|  | 21 | + | 
|  | 22 | +   ```bash | 
|  | 23 | +   git clone https://github.com/your-username/smelly-test.git | 
|  | 24 | +   cd smelly-test | 
|  | 25 | +   ``` | 
|  | 26 | + | 
|  | 27 | +3. **Install Dependencies**   | 
|  | 28 | +   Use npm to install the project dependencies:   | 
|  | 29 | + | 
|  | 30 | +   ```bash | 
|  | 31 | +   npm install | 
|  | 32 | +   ``` | 
|  | 33 | + | 
|  | 34 | +4. **Run the Build**   | 
|  | 35 | +   Compile the project to ensure everything works as expected:   | 
|  | 36 | + | 
|  | 37 | +   ```bash | 
|  | 38 | +   npm run build | 
|  | 39 | +   ``` | 
|  | 40 | + | 
|  | 41 | +5. **Run the Tests**   | 
|  | 42 | +   Verify the functionality by running the tests:   | 
|  | 43 | + | 
|  | 44 | +   ```bash | 
|  | 45 | +   npm test | 
|  | 46 | +   ``` | 
|  | 47 | + | 
|  | 48 | +--- | 
|  | 49 | + | 
|  | 50 | +## Making Contributions | 
|  | 51 | + | 
|  | 52 | +### Submitting Changes | 
|  | 53 | + | 
|  | 54 | +1. **Create a New Branch**   | 
|  | 55 | +   Use a descriptive name for your branch:   | 
|  | 56 | + | 
|  | 57 | +   ```bash | 
|  | 58 | +   git checkout -b feature/your-feature-name | 
|  | 59 | +   ``` | 
|  | 60 | + | 
|  | 61 | +2. **Make Your Changes**   | 
|  | 62 | +   Implement your feature or fix the bug. | 
|  | 63 | + | 
|  | 64 | +3. **Run Tests and Linting**   | 
|  | 65 | +   Before committing, ensure all tests pass and the code adheres to the style guide:   | 
|  | 66 | + | 
|  | 67 | +   ```bash | 
|  | 68 | +   npm test | 
|  | 69 | +   npm run lint | 
|  | 70 | +   ``` | 
|  | 71 | + | 
|  | 72 | +4. **Commit Your Changes**   | 
|  | 73 | +   Write clear and concise commit messages:   | 
|  | 74 | + | 
|  | 75 | +   ```bash | 
|  | 76 | +   git commit -m "feat: add [description of feature or fix]" | 
|  | 77 | +   ``` | 
|  | 78 | + | 
|  | 79 | +5. **Push Your Branch**   | 
|  | 80 | +   Push your branch to your forked repository:   | 
|  | 81 | + | 
|  | 82 | +   ```bash | 
|  | 83 | +   git push origin feature/your-feature-name | 
|  | 84 | +   ``` | 
|  | 85 | + | 
|  | 86 | +6. **Open a Pull Request**   | 
|  | 87 | +   Submit a pull request to the main repository: | 
|  | 88 | +   - **Title**: Provide a concise summary of your changes. | 
|  | 89 | +   - **Description**: Include a detailed explanation of what your pull request does and why it’s needed. | 
|  | 90 | + | 
|  | 91 | +--- | 
|  | 92 | + | 
|  | 93 | +## Code Style | 
|  | 94 | + | 
|  | 95 | +Smelly Test uses a consistent coding style enforced by [ESLint](https://eslint.org/). Ensure your changes adhere to the defined rules. | 
|  | 96 | + | 
|  | 97 | +### Running Linting | 
|  | 98 | + | 
|  | 99 | +To check for code style issues, run:   | 
|  | 100 | + | 
|  | 101 | +```bash | 
|  | 102 | +npm run lint | 
|  | 103 | +``` | 
|  | 104 | + | 
|  | 105 | +--- | 
|  | 106 | + | 
|  | 107 | +## Need Help? | 
|  | 108 | + | 
|  | 109 | +If you encounter any issues or have questions about the project, feel free to: | 
|  | 110 | + | 
|  | 111 | +- Open an [issue](https://github.com/marabesi/smelly-test/issues) in the repository. | 
|  | 112 | + | 
|  | 113 | +--- | 
0 commit comments