|
1 | | -# Contribution Guidelines |
| 1 | +## 📌 Contribution Guidelines |
2 | 2 |
|
3 | 3 | Thank you for your interest in contributing to our project! We welcome all contributions, but to ensure a smooth and collaborative process, please follow these guidelines. |
4 | 4 |
|
5 | | -## How to Contribute |
| 5 | +## 💭 How to Contribute |
6 | 6 |
|
7 | | -1. **Fork the repository** and create a new branch for your feature or bug fix. |
8 | | -2. **Follow the coding style** and conventions used in the project. |
9 | | -3. **Write clear and concise commit messages** that explain the purpose of your changes. |
10 | | -4. **Test your changes thoroughly** before submitting a pull request. |
11 | | -5. **Submit a pull request** with a detailed description of your changes and why they are needed. |
| 7 | +1. **Star** this repository (to support the project) |
| 8 | +2. **Fork** this repository |
| 9 | +3. **Clone** your fork |
| 10 | +4. Create a new **branch** |
| 11 | +5. Add your solution in an appropriate directory structure: |
| 12 | + - First level: Programming language (e.g., `Python/`, `Java/`, `CPP/`) |
| 13 | + - Second level: Your chosen topic (e.g., `trees/`, `arrays/`, `graphs/`) |
| 14 | + - Example: `Python/searching/binary_search.py` or `Java/Trees/BinarySearch.java` |
| 15 | + - Feel free to create new directories if needed |
| 16 | +6. **Commit** and **push** |
| 17 | +7. Open a **Pull Request** |
| 18 | + |
| 19 | +--- |
| 20 | + |
| 21 | +## ✅ Rules |
| 22 | + |
| 23 | +- File naming: `problem_name.language_extension` |
| 24 | +- Comment your code clearly |
| 25 | +- The **problem name must be clearly mentioned** in the comments |
| 26 | +- Avoid duplicate solutions in the same language |
| 27 | +- New solutions for different languages are welcome |
| 28 | + |
| 29 | +--- |
0 commit comments