Is Using Codeberg Instead of GitHub Unprofessional? Real Answers for Job-Seeking Developers

A Real Developer's Dilemma

In the open-source community, an increasing number of developers are paying attention to code hosting platforms beyond GitHub. Codeberg, a nonprofit hosting service based on Forgejo (a Gitea fork), has attracted many users who value open-source principles through its commitment to privacy, ad-free experience, and community-driven governance.

Codeberg runs on Forgejo, which itself is a community hard fork of Gitea, created in late 2022. Gitea was originally forked from the Gogs project and is a lightweight, self-hosted Git service written in Go. When Gitea's governance model sparked community controversy—particularly around disagreements over commercialization direction and decision-making transparency—a group of core contributors decided to create Forgejo, placing it under the governance of Codeberg e.V. (a registered nonprofit organization in Germany). This means Codeberg is not just a code hosting platform, but a governance philosophy in practice: no venture capital involvement, no commercial advertising, and entirely driven by community donations.

However, a representative question recently appeared on Reddit: "Will using Codeberg instead of GitHub be seen as unprofessional and not taken seriously when job hunting in the future?" This developer worried that when everyone else showcases their projects on GitHub, presenting a Codeberg profile page might become a negative mark in job applications.

This question seems simple but actually touches on the subtle relationship between open-source tool choices, personal branding, and career development. It deserves careful consideration from every developer facing the same dilemma.

GitHub's "De Facto Standard" Status

Indeed, GitHub has become the "de facto standard" in software development. As of now, GitHub has over 100 million developer users and is the world's largest code hosting platform. Many recruiters and technical interviewers habitually check candidates' GitHub profiles, examining commit history, project quality, and community engagement.

GitHub's dominant position has deep historical roots. GitHub launched in 2008 and quickly surpassed earlier platforms like SourceForge and Google Code with its elegant web interface and Pull Request workflow. In 2018, Microsoft acquired GitHub for $7.5 billion—an event that itself triggered a massive platform migration discussion, with GitLab reporting several times its normal repository import volume. However, GitHub's network effects ultimately proved its powerful stickiness—the developer social graph, CI/CD ecosystem (GitHub Actions), and deep integration with Microsoft products like VS Code and Copilot make the actual cost of leaving GitHub far higher than emotional dissatisfaction.

This "path dependency" has made GitHub profiles almost a "second resume" for developers. The green contribution heatmap, star counts, and PR records on well-known open-source projects all invisibly constitute a form of "social proof."

However, it's worth noting that GitHub's contribution graph, while visually intuitive, is actually quite controversial in technical hiring circles. Critics point out that the heatmap can easily be artificially inflated—automated commits, trivial documentation changes, and even dedicated "green dot generator" tools can all create an illusion of activity. Additionally, its display of private repository contributions isn't transparent enough. More and more experienced technical interviewers have realized that a fully green heatmap doesn't equal high-quality engineering output—they prefer to deeply read candidates' actual code, Issue discussions, and Code Review records.

For these reasons, the questioner's concerns are not unfounded—in an ecosystem dominated by GitHub, choosing an "alternative" platform may indeed incur some communication costs.

What Recruiters Actually Care About

However, if we deeply analyze what hiring parties actually need, we'll find the key issue isn't "which platform you use" but "what you demonstrate."

Code Quality Trumps Platform Branding

Technical interviewers focus on your code quality, engineering ability, and problem-solving approach. A high-quality project hosted on Codeberg is far more convincing than an empty forked repository on GitHub. The platform itself is merely a vessel—what's truly being evaluated is the content.

Link Accessibility Is What Matters

Regardless of where you host your code, as long as you can provide an accessible link, recruiters can view your work. Codeberg's project pages are equally open and clear, with presentation that doesn't fundamentally differ from GitHub. What actually causes problems is work that's inaccessible or hard to understand, not the platform's "popularity."

Alignment with Open-Source Philosophy Can Be a Plus

For companies and teams that value open-source culture, privacy protection, or decentralization principles, actively choosing a platform like Codeberg might actually demonstrate your deep thinking about technical values—becoming an interesting talking point or even a positive differentiator.

In fact, Codeberg is just one representative of the decentralized code hosting movement. The broader picture also includes Radicle (a peer-to-peer protocol-based code collaboration platform that doesn't rely on any central server), ForgeFed (a standard attempting to interconnect different Forge instances through the ActivityPub protocol, similar to Mastodon's relationship to Twitter), and Software Heritage (a project supported by France's INRIA, dedicated to archiving all of humanity's source code heritage). Together, these projects form a vision: code hosting should not be monopolized by any single commercial entity, and open-source infrastructure itself should also be open source. Understanding and participating in these projects is itself a demonstration of technical vision and value judgment.

Practical Compromise Strategies

For developers who want to use Codeberg but are concerned about career risks, there are more flexible solutions—no need to fall into an "either/or" binary choice.

Multi-Platform Mirror Synchronization

The safest approach is to maintain multiple platforms simultaneously. You can use Codeberg as your primary development platform while mirroring your code to GitHub through Git's multiple remote repository functionality. This way you enjoy Codeberg's philosophical advantages while retaining GitHub's visibility. Many experienced developers employ this "dual insurance" strategy.

From a technical implementation perspective, Git as a distributed version control system natively supports multiple remotes. Developers can use the git remote add command to add multiple push targets for the same local repository, or use git remote set-url --add --push to push to multiple platforms with a single git push. Furthermore, Codeberg itself provides repository mirroring functionality that can automatically push repositories to external platforms like GitHub. Similarly, GitHub Actions or third-party CI tools can also be configured to automatically sync to other Git hosting services on every push. The operational cost of this approach is extremely low—it's virtually "set it once, works forever."

Include Direct Links in Your Resume

Rather than agonizing over platform names, simply include accessible links to specific projects in your resume and portfolio. What recruiters see when they click the link is real code—they won't develop bias just because the domain isn't github.com.

Adjust Flexibly Based on Your Goals

If you're actively job hunting and targeting traditional companies, you might lean toward presenting on GitHub; if your targets are open-source communities, privacy-focused teams, or freelancing, Codeberg is perfectly capable of serving as your storefront. Tools should serve your goals, not constrain your choices.

The Exaggerated "Professionalism" Anxiety

Returning to the original question: Does Codeberg look unprofessional? The answer is—this is largely an exaggerated anxiety.

So-called "professionalism" has never been defined by which hosting platform you use, but rather by your technical ability, code quality, collaborative attitude, and consistent output. A mature hiring team won't question a candidate's professional competence just because they use Codeberg.

What you really need to worry about isn't the platform's "brand," but whether you have presentable work and whether you can clearly demonstrate your engineering capabilities. If this content is solid, it won't be overlooked regardless of where it's hosted.

Conclusion: Let Tools Return to Their Role as Tools

The choice of technical platform is essentially a reflection of personal preference and values. GitHub's ubiquity brings convenience, but it absolutely doesn't mean other platforms are "unprofessional." Codeberg, as a healthy and open open-source ecosystem, is perfectly capable of supporting developers' professional presentation needs.

Rather than being held hostage by the anxiety of "following the crowd," it's better to focus your energy on what truly matters: writing good code, participating in meaningful projects, and expressing yourself clearly. When your abilities are solid enough, the platform is just a detail, not a deciding factor.

For developers who want to embrace open-source ideals while also maintaining a stable job search, multi-platform mirror synchronization is undoubtedly the most rational choice available today.