🟩 As a developer, your lack of GitHub contributions does not necessarily indicate that you aren't good at coding, but it can be a wasted opportunity to confirm that you're passionate and good. 🟩
To help change this, here are four ideas to contribute more to GitHub. 💡
Create a private repo and add at least 1 sentence of what you studied/worked on into a readme at least every weekday. 🟩
Make it your own little journal. 📓
I did not do this but heard of others who have.
It would be good practice for #100DaysOfCode or studying algorithms.
Make a small commit often during the time you code (3 hours a weekday at minimum is best)
Get something to finally work? Commit 🟩
Ending the day? Commit a WIP (work in progress) 🟩
Branching off and trying something that might break the app? Commit working code first 🟩
Create issues for projects 👍
See something that needs to be developed❓
Click "New Issue" and fill in the details. 🟩
Keep tasks small — think "Is it doable in a sprint or two?"
Web devs work with an issue every day, e.g. "feat: create responsive navbar with bootstrap"
Remember that your GitHub graph is not you or where you find your value, but it doesn't give a good impression if it's completely empty. ⬜️ 😬
When your graph is on fire, then people see you as someone who shows up and knows GitHub and git concepts.🔥
At best, you're a competent professional rather than a novice that must be guided, or worse you're just lazy.
Take initiative and do something to show what you know, especially if you're self-taught.
This list isn't exhaustive. There are many ways to contribute like forking a repo, making a pull request, reviewing code, etc.
Activity on GitHub is a great way to showcase your expertise and allow them to cut past questions about what you do and don't know.
Recruiters and hiring managers do look at it, so why not leave a great impression because guess what? It costs you nothing to be active on GitHub.
I would highly suggest improving your graph with these small steps first, then branching out. 🌳
Pun intended. 😉