Update README.md

Author: JRS296

README.md

@@ -1,14 +1,68 @@
-# LeetCode-Solutions
+# Contributing to LeetCode-Solutions
 
-LeetCode Solutions of JRS296.
+Thank you for considering contributing to **LeetCode-Solutions**! This repository is a collection of solutions to LeetCode problems in multiple programming languages. Please read the following guidelines to ensure a smooth contribution process.
 
+## 🛠 How to Contribute
 
-Tags:
+1. **Fork the repository**: Click on the **Fork** button at the top right corner of this page.
+2. **Clone your fork**: 
+   ```sh
+   git clone https://github.com/your-username/LeetCode-Solutions.git
+   ```
+3. **Create a new branch**: 
+   ```sh
+   git checkout -b feature/your-feature-name
+   ```
+4. **Add your solution** following the structure below:
+   - Each problem should be a separate folder named using the format:
+     ```
+     #num - Name - Difficulty
+     ```
+     Example:
+     ```
+     #1 - 2 Sum - Easy
+     ```
+   - Inside the folder, include solutions in different languages and a Markdown file explaining the solution. Example:
+     ```
+     #1 - 2 Sum - Easy
+     ├── 2 Sum - Solution.java
+     ├── 2 Sum - Solution.cpp
+     ├── 2 Sum - Solution.py
+     ├── 2 Sum - Explanation.md
+     ```
+5. **Commit your changes**: Use the following format for commit messages:
+   ```sh
+   git commit -m "Solution #num - Creator/Edited - Date"
+   ```
+   or for explanations:
+   ```sh
+   git commit -m "Explanation #num - Creator/Edited - Date"
+   ```
+6. **Push your branch**:
+   ```sh
+   git push origin feature/your-feature-name
+   ```
+7. **Create a Pull Request (PR)**: Go to the repository on GitHub and click "New Pull Request".
 
-I - Important
+## 📌 Contribution Guidelines
 
-R - Revise
+- **Follow the folder and file structure** as outlined above.
+- **Commit Messages**: Ensure that commit messages follow the specified format.
+- **Pull Requests**: Keep PRs focused and limited to a single problem solution or explanation.
+- **Discussions**: Use GitHub Issues for bug reports, feature requests, or discussions before implementing major changes.
+- **Documentation**: Ensure that the `Explanation.md` file is well-written and clearly explains the approach used in the solutions.
 
-G - Good
+## 🚀 Issue Tracking
 
-L - Learn
+- If you find an issue with an existing solution or have a suggestion, please [open an issue](https://github.com/Dijkstra-Edu/LeetCode-Solutions/issues).
+- When reporting issues, include relevant details such as problem number, expected vs. actual behavior, and language-specific concerns.
+
+## 📜 License
+
+By contributing, you agree that your contributions will be licensed under the repository's license.
+
+## 💬 Need Help?
+
+If you have any questions, feel free to open an issue or start a discussion in the repository.
+
+Happy coding! 🎉