How to Keep Your Work Commits on Your Personal GitHub Profile
Around 2018, when I started college, I created my GitHub account.
In 2022, when I got my first job as a software developer, I had to create my first professional account. That's when I started wondering:
How could I keep my work contributions on my personal GitHub profile?
The answer was simpler than I expected.
Your work commits can show up on your personal profile
Since I started working, I've used my professional email address for my Git commits.
By associating that email address with my personal GitHub account, my contributions can appear on my personal profile, even when I'm working on repositories owned by different companies.
I've worked at two companies so far, and my contributions from college also show up on my profile.
Of course, this doesn't mean I can access the source code of every repository I've contributed to.
Private repositories remain private. You can't inspect their code, check whether they have a README, or evaluate their implementation without the necessary permissions.
Even I can lose access to a company's repositories when I leave the organization.
But my contribution history can still be part of my personal GitHub profile.
Does an inactive GitHub profile mean an inactive developer?
I recently came across a discussion on LinkedIn about evaluating developers based on their GitHub activity, particularly when hiring senior engineers.
I don't think commit frequency on a personal GitHub profile is a reliable way to measure someone's experience.
Not every developer can publish their work publicly. Many contribute primarily to private company repositories, and some companies use different platforms for version control.
A developer might have years of experience building production systems without having a single public repository that reflects the complexity of their work.
And let's be honest: every company has its own way of working.
Some teams prioritize extensive documentation. Others follow the philosophy of "if it works, it works."
There are also programming principles that encourage writing code that communicates its intent clearly, reducing the need for unnecessary comments.
And what about README files?
I'll save that discussion for another day.
How to set it up
If you want your work contributions to appear on your personal GitHub profile, start by checking which email address you're using for your Git commits.
You can inspect it with:
git config user.email
If you're using your professional email, make sure that address is also associated with your personal GitHub account.
You can manage your email addresses in your GitHub account settings.
A few things to keep in mind:
- Email association matters. GitHub uses the email address associated with a commit to link it to your account.
- Private contributions can be displayed. GitHub lets you choose whether to show anonymized contributions from private repositories on your profile.
- Not every commit necessarily counts. Contributions must meet GitHub's eligibility criteria, so simply associating an email address doesn't guarantee that every commit will appear in your contribution graph.
You can find more details in the GitHub documentation about contributions.
If you're unsure how to configure everything, you can also ask an AI assistant to walk you through the process.
Final thoughts
I'm not suggesting that GitHub activity is irrelevant when evaluating a developer. Personal projects can be great ways to demonstrate technical skills, problem-solving abilities, and architectural decisions.
My point is simply that an inactive-looking GitHub profile doesn't necessarily tell the whole story.
Before assuming a developer has stopped learning or contributing, remember that much of their work might happen behind private repositories and company accounts.
Sometimes, the contributions are there. You just need to understand how GitHub tracks them.
Have you ever had to deal with multiple GitHub accounts for personal and professional work? How do you manage your contributions?
Top comments (0)