|
| 1 | +# Contribution Guidelines |
| 2 | + |
| 3 | +Thank you for considering contributing to Skill Issues Killer! We welcome contributions of all kinds, whether you're adding a new project, improving existing features, or fixing bugs. Below are the guidelines to help you get started. |
| 4 | + |
| 5 | +## Adding a New Project |
| 6 | + |
| 7 | +To contribute a new project, please ensure your addition includes the following: |
| 8 | + |
| 9 | +1. **Project Specification** |
| 10 | + - Create a detailed specification of the project in a markdown file. |
| 11 | + - The specification should include examples and clearly explain the requirements and objectives of the project. |
| 12 | + |
| 13 | +2. **Comprehensive Test Suite** |
| 14 | + - Provide a comprehensive test suite to validate the project. |
| 15 | + - The test suite should be programming language agnostic (tests at the API level). |
| 16 | + - Include a Dockerfile to run the test suite. |
| 17 | + |
| 18 | +3. **Docker Compose File** |
| 19 | + - Provide a docker-compose file. |
| 20 | + - This file should instrument the user's API implementation with the test suite, ensuring that the tests are executed correctly. |
| 21 | + |
| 22 | + |
| 23 | +## Contributing Features, Fixes, or Improvements |
| 24 | + |
| 25 | +If you want to contribute by adding new features, fixing issues, or making other improvements, please follow these steps: |
| 26 | + |
| 27 | +1. **Fork the Repository** |
| 28 | + - Fork the repository to your own GitHub account. |
| 29 | + |
| 30 | +2. **Make Your Changes** |
| 31 | + - Make the necessary changes in your forked repository. |
| 32 | + |
| 33 | +3. **Submit a Pull Request (PR)** |
| 34 | + - Create a PR to suggest your changes. |
| 35 | + - Ensure your PR is well-documented, explaining the changes and why they are necessary. |
0 commit comments