Give credit to Open Source Contributors

give-credit-to-open-source-contributors

Tables like this one are in a lot of repositories, giving well deserved credit to their contributors.

And you know, developers are lazy so there has to be an automation to manage this.

All contributors

Today’s topic is the all-contributors tool and I will show you how you can integrate it in your project and why you should!

Contributors merging a PR will get a green square in their profile, but not every contribution is actually submitted through a pull request.

That’s why there’s an emoji key table which includes many other actions giving value to the project, such as writing blog posts, mentoring new contributors or answering questions on discord.

Here’s a video where I talk about the two main ways to use this tool which are the Bot and the CLI.

Bot

The bot is a GitHub App that will automatically create a Pull Request to add a new contributor to the table.

Once installed, you can invoke it with a comment in an issue or pull request, like this:

@all-contributors please add @balastrong for code

Pros are that it’s automatic, you literally just have to write a comment and the bot will do the rest with the PR ready to be merged.
Cons, it spams a little bit of notifications.

CLI

Similarly to the bot, once installed in your project you can run the CLI to add a new contributor to the table.

npx all-contributors add balastrong code

Pros: you can control when/how you want to add contributors as it just edits the files locally.
Cons: as it’s less automagic, you will need to manually commit and push the changes.

Hacktoberfest

A cool contribution during Hacktoberfest could be asking the repository maintainers if they’re interested in using the tool.

Setting it up can be a cool PR, after receiving the green light on an issue 🙂

Conclusion

Which one is better? I definitely think it depends on how you want to use it, but both ways are super easy to set up and use.

I’m using it on my github-stats community project and I think it’s a great way to say thank you to everyone involved in the success of an open source project.

Want to learn more? You can watch my video or directly head over the all-contributors website.

Thanks for reading this article, I hope you found it interesting!

I recently launched my Discord server to talk about Open Source and Web Development, feel free to join: https://discord.gg/bqwyEa6We6

Do you like my content? You might consider subscribing to my YouTube channel! It means a lot to me ❤️
You can find it here:
YouTube

Feel free to follow me to get notified when new articles are out 😉

Total
0
Shares
Leave a Reply

Your email address will not be published. Required fields are marked *

Previous Post
seo-writing:-13-tips-on-writing-blog-posts-that-rank-on-google

SEO Writing: 13 Tips on Writing Blog Posts That Rank on Google

Next Post
building-an-ai-chatbot-using-flutter-with-makersuite-and-palm-api:-a-step-by-step-guide

Building an AI Chatbot using Flutter with Makersuite and Palm API: A Step-by-Step Guide

Related Posts

網紅程式設計師回應炒股一年虧130萬:當流量主體走進散戶敘事,虧損也成了內容

一位擁有技術背景的網紅程式設計師公開承認一年在股市虧損約130萬人民幣並回應爭議。本文拆解事件經過、散戶在高波動市場的結構性劣勢,以及科技自媒體與投資敘事的邊界。 Techroomage 編輯部 · 2026年7月1日 · 閱讀約 8 分鐘 一年虧掉130萬。當這個數字出現在一個以理性、技術背景為人設的網紅程式設計師身上,它不再是單純的帳面損失,而變成了一則被演算法與留言區共同咀嚼的內容事件。微博熱搜「網紅程式設計師回應炒股1年虧130萬」之所以快速發酵,在於它踩中了一個尷尬的對比:一個理論上最懂數據、最擅長建立模型的羣體,在公開市場裡依然難以免疫散戶的宿命。 TL;DR 一位在微博具有相當關注度的網紅程式設計師公開回應「炒股一年虧損約130萬人民幣」的傳聞,承認虧損屬實並對外說明。事件折射出科技自媒體人物把個人投資經歷內容化的新趨勢,也再次暴露散戶在高波動市場中的資訊劣勢與情緒管理難題。 事件經過 熱搜話題源於這位程式設計師在社羣平臺上揭露自己過去一年累計虧損約130萬人民幣的紀錄,隨後引發大量轉發與討論。當事人隨後親自下場回應,針對外界質疑做出說明。 需要強調的是,130萬這個數字來自當事人自述與微博話題傳播,並未經第三方財報或券商資料獨立核實;其部位結構(個股、ETF、是否含融資槓桿)也未有完整公開。引用時應保留這層不確定性,避免把自述數字當成可查證的財務事實。 關鍵事實(條列) 事件主角:一位在中國社羣平臺具有技術人設、被網友稱為「網紅程式設計師」的內容創作者 關鍵數字:自述一年累計虧損約130萬人民幣(來源為當事人公開發言,未經獨立核實)…
Read More