https://github.com/trulyaman25/leetcode_solutions

Welcome to my LeetCode solutions repository! Here you'll find my solutions to various LeetCode problems, categorized by their respective difficulty levels.
https://github.com/trulyaman25/leetcode_solutions

Last synced: 13 days ago
JSON representation

Welcome to my LeetCode solutions repository! Here you'll find my solutions to various LeetCode problems, categorized by their respective difficulty levels.

• Host: GitHub
• URL: https://github.com/trulyaman25/leetcode_solutions
• Owner: trulyaman25
• Created: 2024-05-12T18:36:23.000Z (9 months ago)
• Default Branch: main
• Last Pushed: 2025-01-01T18:25:07.000Z (24 days ago)
• Last Synced: 2025-01-01T19:27:01.874Z (24 days ago)
• Language: C++
• Homepage:
• Size: 336 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# LeetCode Solutions

Welcome to my LeetCode solutions repository! Here you'll find my solutions to various LeetCode problems, categorized by their respective difficulty levels.

## Structure

- **Easy Problems**: Contains solutions to LeetCode problems categorized as easy.

- **Medium Problems**: Contains solutions to LeetCode problems categorized as medium.

- **Hard Problems**: Contains solutions to LeetCode problems categorized as hard.

- **Other**: Contains additional resources, notes, or miscellaneous code related to LeetCode.

## Usage

Each problem solution is organized in its own folder, named according to the problem's title on LeetCode. Inside each folder, you'll find the following files:

- **README.md**: Contains the problem statement and a detailed explanation of the approach used to solve the problem.

- **Solution.cpp** (or .py, .java, etc.): Contains the code implementation of the solution in Java (or Python, C++, etc.).

- **TestCases.txt**: Contains sample test cases to validate the solution.

Feel free to explore the solutions and learn from them. You can also contribute by submitting pull requests with your own solutions or improvements to existing ones.

## Contribution Guidelines

If you'd like to contribute to this repository, please follow these guidelines:

1. Fork the repository.

2. Create a new branch (`git checkout -b feature/add-solution`).

3. Make your changes and commit them (`git commit -am 'Add solution to Problem XYZ'`).

4. Push your changes to your forked repository (`git push origin feature/add-solution`).

5. Open a pull request with a clear description of your changes.

## Feedback

If you have any feedback, suggestions, or improvements for the existing solutions, feel free to open an issue or reach out to me directly.

Happy coding!