Skip to content

Commit f32cb39

Browse files
iamAntimPaliamAntimPal
authored
Merge pull request #59 from iamAntimPal/Branch-1
Branch 1
2 parents d102b27 + 2585b7a commit f32cb39

File tree

2 files changed

+170
-8
lines changed

2 files changed

+170
-8
lines changed

‎CONTTRIBUTE.MD‎

Lines changed: 170 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,170 @@
1+
# Contributing to LeetCode_Daily_Task
2+
3+
Thank you for your interest in contributing to **LeetCode_Daily_Task**!
4+
5+
---
6+
7+
## Table of Contents
8+
- [Contributing to LeetCode\_Daily\_Task](#contributing-to-leetcode_daily_task)
9+
- [Table of Contents](#table-of-contents)
10+
- [How to Contribute](#how-to-contribute)
11+
- [Impressive Contributions \& Highlights](#impressive-contributions--highlights)
12+
- [Contributor Recognition Process](#contributor-recognition-process)
13+
- [Share Your Thoughts](#share-your-thoughts)
14+
- [Issue Reporting](#issue-reporting)
15+
- [Pull Request Process](#pull-request-process)
16+
- [Coding Guidelines](#coding-guidelines)
17+
- [Commit Message Guidelines](#commit-message-guidelines)
18+
- [Acknowledgments](#acknowledgments)
19+
20+
---
21+
22+
## How to Contribute
23+
24+
1. **Fork the Repository:**
25+
Click the **Fork** button on the repository page to create your own copy.
26+
27+
2. **Clone Your Fork:**
28+
```bash
29+
git clone https://github.com/your-username/LeetCode_Daily_Task.git
30+
```
31+
32+
3. **Create a Branch:**
33+
Create a new branch for your feature, solution, or bug fix.
34+
```bash
35+
git checkout -b feature/your-feature-name
36+
```
37+
38+
4. **Implement Your Changes:**
39+
- Add your solution or enhancements.
40+
- Include any discussion points or explanations in your code comments or PR description.
41+
- Follow the coding guidelines (see below).
42+
- Update or add test cases as needed.
43+
44+
5. **Commit Your Changes:**
45+
Use clear and descriptive commit messages (see Commit Message Guidelines).
46+
47+
6. **Open a Pull Request:**
48+
Submit a pull request (PR) with a clear title and description outlining your changes, and reference any related issues.
49+
50+
---
51+
52+
## Impressive Contributions & Highlights
53+
54+
We love to see innovative and creative solutions! This section is dedicated to showcasing impressive contributions that go beyond the daily task:
55+
56+
- **What to Share:**
57+
- **Enhanced Solutions:** Share optimized, creative, or particularly elegant approaches to LeetCode problems.
58+
- **Detailed Explanations:** Provide in-depth explanations and insights that help others understand your reasoning.
59+
- **Additional Context:** Include performance comparisons, alternative methods, or advanced techniques.
60+
61+
- **How to Get Recognized:**
62+
The first contributor to submit an impressive solution for a given challenge will have their name highlighted in this section. For example:
63+
```md
64+
**Impressive Contribution by:** @username
65+
```
66+
To be recognized, please send an email with your GitHub username and Gmail address to **[email protected]**. This helps us track and celebrate innovative contributions.
67+
68+
- **Discussion:**
69+
Engage with others by discussing alternative approaches or asking questions in the issue tracker or PR comments. Your input can help refine the solution and inspire further improvements.
70+
71+
*Feel free to update this section with new highlights, alternative methods, or breakthrough approaches that push the boundaries of problem-solving.*
72+
73+
---
74+
75+
## Contributor Recognition Process
76+
77+
- **How It Works:**
78+
Exceptional contributions are recognized to encourage innovative thinking.
79+
80+
- **Steps to Get Recognized:**
81+
1. Submit your solution via a PR.
82+
2. Once your PR is merged, send an email with your GitHub username and Gmail address to **[email protected]**.
83+
3. Your details will be added to the "Impressive Contributions & Highlights" section for that challenge.
84+
85+
This process helps build an active community and rewards creativity and excellence.
86+
87+
---
88+
89+
## Share Your Thoughts
90+
91+
We welcome your feedback and ideas!
92+
- **Questions & Suggestions:** Open an issue or start a discussion if you have ideas for improvements, new challenges, or if you need help.
93+
- **Solution Explanations:** Share your approach and insights to help others understand the problem better.
94+
- **Improvements:** If you see a more efficient or elegant solution, feel free to contribute your version.
95+
96+
---
97+
98+
## Issue Reporting
99+
100+
- **Found a Bug or Have a Suggestion?**
101+
Open a new issue on GitHub with a descriptive title and details on how to reproduce the problem or suggest improvements.
102+
- **Include the Following Information:**
103+
- A clear explanation of the issue.
104+
- Steps to reproduce the problem.
105+
- Environment details if applicable (e.g., OS, specific LeetCode problem IDs).
106+
107+
---
108+
109+
## Pull Request Process
110+
111+
1. **Ensure Tests Pass:**
112+
Verify that your changes pass all existing tests. If you’re adding new functionality, please include corresponding tests.
113+
114+
2. **Provide a Descriptive Title:**
115+
Your PR title should succinctly describe your changes (e.g., "Add optimized solution for Two Sum challenge").
116+
117+
3. **Detailed Description:**
118+
In your PR, include:
119+
- The purpose of your changes.
120+
- Instructions on how to test your changes.
121+
- Additional context, screenshots, or references to related issues.
122+
- If you're submitting an impressive solution, include a note so we can update the recognition section.
123+
124+
4. **Review & Feedback:**
125+
Your PR will be reviewed by the maintainers. Please address any feedback or requested changes promptly.
126+
127+
---
128+
129+
## Coding Guidelines
130+
131+
- **Consistent Formatting:**
132+
Follow the repository’s established style for code formatting, naming conventions, and folder structure.
133+
134+
- **Comment Your Code:**
135+
Provide clear comments explaining your logic, especially for complex solutions.
136+
137+
- **Efficiency and Readability:**
138+
Ensure your solutions are optimized for performance and are easy to understand.
139+
140+
- **Documentation:**
141+
Update or add documentation if your changes affect existing functionality.
142+
143+
---
144+
145+
## Commit Message Guidelines
146+
147+
- **Short & Descriptive:**
148+
The first line of your commit message should be a brief summary (50 characters or less).
149+
150+
- **Imperative Mood:**
151+
Use the imperative mood (e.g., "Add", "Fix", "Update").
152+
153+
- **Detailed Description:**
154+
If necessary, include a detailed description after the first line, separated by a blank line.
155+
156+
Example:
157+
```txt
158+
Add solution for Two Sum problem
159+
160+
This commit introduces an optimized solution for the Two Sum problem, along with test cases and documentation.
161+
```
162+
163+
---
164+
165+
## Acknowledgments
166+
167+
Thank you for contributing to **LeetCode_Daily_Task**!
168+
Your help and commitment make this project a valuable resource for the community. If you have any questions or need further assistance, feel free to open an issue or contact the maintainers.
169+
170+
> ## Happy coding and happy LeetCoding! 🚀

‎README.md‎

Lines changed: 0 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -45,14 +45,6 @@ Problem 3: Description of the problem and the SQL solution.
4545
Feel free to fork this repository, suggest improvements, or submit your own solutions via pull requests. Let's learn and grow together!
4646

4747

48-
### Progress
49-
<progress value="75" max="100"></progress>
5048
### Progress
5149
🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩⬜⬜⬜⬜⬜ 75%
5250

53-
54-
55-
update-date.yml
56-
57-
58-
## Last Updated: 2023-10-25

0 commit comments

Comments
 (0)