Tag solutions by topic (arrays, strings, DP, graphs, and so on)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- Under an hour
- Newbie friendliness
- 88/100
Research direction
Choose 10 solution files and read their headers to identify each problem's main algorithm topics. Add a lowercase, comma separated Topic: line to each header, then review the files to confirm all 10 are tagged consistently. Comment with the files you plan to edit to avoid overlap.
Written by the indexing model from the issue text.
Description
It is hard to find a solution by topic right now. A simple Topic: line in the header would fix that and make the index script (if someone builds it) much more useful.
Time: about 30 minutes
Skills: knowing common algorithm categories
What to do
- Add a line like
# Topic: arrays, hash mapto the header of 10 solutions - Use lowercase, comma separated tags
- Common tags: arrays, strings, hash map, two pointers, sliding window, recursion, sorting, binary search, linked list, trees, graphs, dp, math
Comment with the files you are taking so we do not overlap.
Who can take this
Anyone. Beginners, experienced developers, students, and people who do not code. Any language, any level. If you want to help, you are welcome here.
How to contribute
- Comment on this issue so nobody else starts the same thing
- Fork the repo
- Clone your fork and create a branch
- Make your change
- Commit, push, and open a Pull Request
Never opened a pull request before? Start with First Contributions or watch this walkthrough.
Stuck on anything? Ask in the comments. Basic questions are fine.
If this repo helps you or you like where it is going, a star is a nice way to say thanks and helps other people find it. Entirely optional, and you do not need it to contribute.
- Dominant language
- Python
- Stars
- 3
- Forks
- 2
- Avg merge
- 4h 17m
- Merged PRs (30d)
- 12
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Huerte/algo-solutions-python
-
5-minutes all-levels beginner-friendly codewars documentation good first issue hackerrank hacktoberfest interview-prep leetcode no-code-needed open-source students
Difficulty 1/5 1-3 hours Newbie friendliness 72/100
Huerte/algo-solutions-python#154 ·
Maintainers usually reply within 1 day
-
15-minutes 5-minutes algorithm any-language beginner-friendly c cpp csharp easy go good first issue hacktoberfest help wanted java javascript kotlin python rust swift typescript
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Huerte/algo-solutions-python#151 ·
Maintainers usually reply within 1 day
-
5-minutes algorithm all-levels any-language beginner-friendly codewars easy good first issue hackerrank hacktoberfest help wanted interview-prep leetcode open-source students
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Huerte/algo-solutions-python#144 · 1 comment ·
Maintainers usually reply within 1 day
-
5-minutes all-levels beginner-friendly codewars documentation good first issue hackerrank hacktoberfest interview-prep leetcode no-code-needed open-source students
Difficulty 2/5 Under an hour Newbie friendliness 68/100
Huerte/algo-solutions-python#140 ·
Maintainers usually reply within 1 day
-
15-minutes 5-minutes algorithm any-language beginner-friendly c cpp csharp easy go good first issue hacktoberfest help wanted java javascript kotlin python rust swift typescript
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Huerte/algo-solutions-python#138 ·
Maintainers usually reply within 1 day
All issues in Huerte/algo-solutions-python
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
elviskahoro/sdk-python-attio#144 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
RenyiELBO raises TypeError when model has no sample sitesPossibly taken @alibb007 claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day