Add contributors section to README 🏆
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 90/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- markdown
- Domain
- documentation
Research direction
Open README.md and find a suitable place for the supplied contributors section. Add the heading, thank-you text, and contributors image link from the issue; the task is done when the section appears in the README and links to the repository’s contributors graph.
Written by the indexing model from the issue text.
Description
Add contributors section to README 🏆
File: README.md
README has no shoutout to contributors 💀
They worked hard and deserve credit fr!!
Fix: add this section to README.md:
🏆 Contributors
Thanks to all the amazing people
who have contributed to DevBoard!
Just add that image link to README.md!!
It auto-updates with every new contributor 🔥
No code needed — pure markdown!!
- Dominant language
- JavaScript
- Stars
- 39
- Forks
- 105
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 28
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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 anoopcodehack/DevBoard
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
anoopcodehack/DevBoard#588 ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
anoopcodehack/DevBoard#587 ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 1/5 Under an hour Newbie friendliness 90/100
anoopcodehack/DevBoard#586 ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
anoopcodehack/DevBoard#584 ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
anoopcodehack/DevBoard#583 ·
Maintainers usually reply within 1 day
All issues in anoopcodehack/DevBoard
Similar issues
-
check:passed feeds:remove
Difficulty 1/5 Under an hour Newbie friendliness 65/100
iptv-org/database#37176 · 1 comment · 1 reaction ·
Maintainers usually reply within 9 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
hawk-digital-environments/HAWKI#443 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
feedback simulation workshop
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
githubnext/gh-aw-workshop#4370 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
AltimateAI/vscode-dbt-power-user#2089 ·