|
| 1 | +# LeetCode_Daily_Task |
1 | 2 |
|
2 | | -# Contributing to leetcode-SQL-Database |
3 | | - |
4 | | -We appreciate your interest in contributing to **leetcode-SQL-Database**! |
5 | | -This repository hosts SQL and Database solutions for LeetCode challenges. Your contributions help make this a valuable resource for everyone. |
6 | | - |
7 | | ---- |
8 | | - |
9 | | -## Table of Contents |
10 | | -- [Contributing to leetcode-SQL-Database](#contributing-to-leetcode-sql-database) |
11 | | - - [Table of Contents](#table-of-contents) |
12 | | - - [How to Contribute](#how-to-contribute) |
13 | | - - [Issue Reporting](#issue-reporting) |
14 | | - - [Pull Request Process](#pull-request-process) |
15 | | - - [Coding Guidelines](#coding-guidelines) |
16 | | - - [Commit Message Guidelines](#commit-message-guidelines) |
17 | | - - [Acknowledgments](#acknowledgments) |
| 3 | +This repository tracks my daily progress on LeetCode, helping me achieve my coding goals. Each solution is optimized for efficiency and readability, covering topics like arrays, strings, dynamic programming, graphs, and algorithms. Committed to solving problems daily to improve problem-solving skills and consistency! 💡🔥 |
18 | 4 |
|
19 | 5 | --- |
20 | 6 |
|
21 | | -## How to Contribute |
22 | | - |
23 | | -1. **Fork the Repository:** |
24 | | - Click the **Fork** button on the repository page to create your own copy. |
25 | | - |
26 | | -2. **Clone Your Fork:** |
27 | | - ```bash |
28 | | - git clone https://github.com/your-username/leetcode-SQL-Database.git |
29 | | - ``` |
30 | | - |
31 | | -3. **Create a Branch:** |
32 | | - Create a new branch for your feature or bug fix. |
33 | | - ```bash |
34 | | - git checkout -b feature/your-feature-name |
35 | | - ``` |
36 | | - |
37 | | -4. **Implement Your Changes:** |
38 | | - - Add new solutions or improve existing ones. |
39 | | - - Follow the coding guidelines (see below). |
40 | | - - Update or add test cases as needed. |
| 7 | +## LeetCode Daily Task 🚀 |
41 | 8 |
|
42 | | -5. **Commit Your Changes:** |
43 | | - Follow the commit message guidelines to ensure clarity. |
| 9 | +This repository is dedicated to my daily LeetCode practice, serving as a personal tracker for problem-solving progress. It covers a wide range of topics including: |
44 | 10 |
|
45 | | -6. **Open a Pull Request:** |
46 | | - Submit a pull request (PR) with a clear title and description outlining your changes and referencing any related issues. |
| 11 | +- **Arrays** |
| 12 | +- **Strings** |
| 13 | +- **Dynamic Programming (DP)** |
| 14 | +- **Graphs** |
| 15 | +- **Algorithms** |
| 16 | +- **And more...** |
47 | 17 |
|
48 | 18 | --- |
49 | 19 |
|
50 | | -## Issue Reporting |
| 20 | +## Goals & Achievements |
51 | 21 |
|
52 | | -- **Found a Bug or Have a Suggestion?** |
53 | | - Open a new issue on GitHub with a descriptive title and details on how to reproduce the problem or implement the feature. |
54 | | -- **Include Information:** |
55 | | - - A clear explanation of the issue. |
56 | | - - Steps to reproduce the bug. |
57 | | - - Environment details if applicable (e.g., SQL version, OS). |
| 22 | +- **Daily Challenge:** Solve at least one LeetCode problem every day. |
| 23 | +- **Skill Improvement:** Enhance problem-solving skills and coding efficiency. |
| 24 | +- **Progress Tracking:** Review solutions regularly for continuous improvement. |
| 25 | +- **Data Structures & Algorithms:** Strengthen knowledge through consistent practice. |
58 | 26 |
|
59 | 27 | --- |
60 | 28 |
|
61 | | -## Pull Request Process |
62 | | - |
63 | | -1. **Ensure Tests Pass:** |
64 | | - Verify that your changes pass all existing tests and add new tests if necessary. |
65 | | - |
66 | | -2. **Provide a Descriptive Title:** |
67 | | - Your PR title should succinctly describe your changes. |
68 | | - |
69 | | -3. **Detailed Description:** |
70 | | - Include: |
71 | | - - The purpose of the changes. |
72 | | - - How to test your changes. |
73 | | - - Any additional context or screenshots. |
74 | | - |
75 | | -4. **Review & Feedback:** |
76 | | - Your PR will be reviewed by the maintainers. Feedback may be provided—please address any requested changes. |
| 29 | +## Features |
77 | 30 |
|
78 | | ---- |
79 | | - |
80 | | -## Coding Guidelines |
81 | | - |
82 | | -- **Consistent Formatting:** |
83 | | - Follow the repository’s existing style for code and SQL queries. |
84 | | - |
85 | | -- **Comment Your Code:** |
86 | | - Write clear comments to explain complex logic. |
87 | | - |
88 | | -- **Optimized Queries:** |
89 | | - Ensure that your SQL solutions are optimized and formatted properly. |
90 | | - |
91 | | -- **Documentation:** |
92 | | - Update documentation or add comments in your code if needed. |
| 31 | +- ✅ **Daily Problem Solutions** – Organized by date and topic. |
| 32 | +- ✅ **Optimized Code** – Focused on efficiency and readability. |
| 33 | +- ✅ **Topics Covered** – Arrays, Strings, Linked Lists, Trees, DP, Graphs, and more. |
| 34 | +- ✅ **Well-Commented Code** – Explaining the thought process behind each solution. |
93 | 35 |
|
94 | 36 | --- |
95 | 37 |
|
96 | | -## Commit Message Guidelines |
97 | | - |
98 | | -- **Short & Descriptive:** |
99 | | - The first line of your commit message should be a brief summary (max 50 characters). |
100 | | - |
101 | | -- **Imperative Mood:** |
102 | | - Use the imperative mood (e.g., "Add", "Fix", "Update"). |
103 | | - |
104 | | -- **Detailed Description:** |
105 | | - If necessary, add a longer description after the first line, separated by a blank line. |
| 38 | +## Contributing |
106 | 39 |
|
107 | | -Example: |
108 | | -```txt |
109 | | -Add solution for two-sum SQL query |
110 | | -
|
111 | | -This commit adds an optimized SQL query to solve the two-sum problem. |
112 | | -``` |
| 40 | +I welcome contributions that improve or extend this repository. If you'd like to contribute, please check out the [CONTRIBUTING.md](CONTRIBUTING.md) file for more details on how to get started. |
113 | 41 |
|
114 | 42 | --- |
115 | 43 |
|
116 | | -## Acknowledgments |
117 | | - |
118 | | -Thank you for contributing to **leetcode-SQL-Database**! |
119 | | -Your help is greatly appreciated and makes this project a better resource for the community. If you have any questions, feel free to reach out through an issue or discussion. |
120 | | - |
121 | | -> ## Happy coding and happy SQL querying! 🚀 |
| 44 | +Join me on this journey of mastering coding—one problem at a time! |
| 45 | +Happy coding and happy LeetCoding! 💡🔥 |
0 commit comments