Share Your Private Gitea / Forgejo Repo with Recruiters in 1 Minute

Here’s the easiest way to generate a secure share link for gitea.com, self-hosted gitea or forgejo

3 min read · Feb 15, 2026

Background

If you self-host your code on Gitea or Forgejo or simply gitea.com, chances are your repositories are private by default.

That’s great for control, privacy and security — but not so great when a recruiter asks:

“Can you share your code or attach your github?”

• Making the repo public means giving away your potential intellectual property.
• Creating accounts and making the recruiters collaborators on the repo is unnecessary and tedious friction.
• Sending ZIP files looks unprofessional and clumsy especially if there are multiple codeprojects.

You need a quick, clean way to share private code — view-only.

I ran into this problem while job hunting — my best work lives on my private passion-projects and on my self-hosted instances, and none of the options above felt right or effective solutions.
I needed a quick, clean way to share private code — view-only.

The Simple Solution: ShareMyGit

ShareMyGit lets you generate a secure link to your private repository without making it public.

No mirroring.
No repo duplication.
No account creation for viewers.

Just a link.

How It Works (Quick Steps)

1. Go to sharemygit.com
2. Sign in with your gitea.com or self-hosted Gitea / Forgejo account
3. Select the private repository
4. Generate a share link or copy the portfolio link

That’s it.

Self-Hosted: 3 Additional Steps

For the self-hosted approach there are 3 additional steps:

1. Go to your Gitea/Forgejo Settings → Applications
2. Enable “Confidential Client”
3. Copy Client ID and Secret above

Like below.

And that’s it!

What Recruiters See

With the link, recruiters can:

• Browse files
• Read source code
• View project structure
• Check README/docs
• Download project as zip for local testing

They cannot:

• Push code
• Modify anything
• Access your actual gitea/forgejo/gitea.com account

It’s safe, read-only visibility.

Why This Is Better Than Making Repos Public

Public repo 👎

• Permanently expose your code to indexers and crawlers forever
• You’re giving away your intellectual property for free
• Your code gets indexed by search engines
• Your code gets scraped / cloned freely

ShareMyGit link 👍

• Private repo stays private
• You’re keeping personal projects and potential business ideas private
• Controlled sharing to only a select few which you revoke at any time
• Professional presentation
• Limited accessibility
• Perfect for portfolio reviews

When to Use It

Use ShareMyGit when:

• Applying for jobs
• Sending coding samples privately
• Showcasing side projects
• Sharing take-home assignments
• Sharing school assignments as teacher/educator

It removes friction while keeping control.

Pro Tip: Add the Portfolio Link to Your CV

Instead of sharing links one repo at a time, attach your ShareMyGit portfolio link directly to your CV. Recruiters can browse all your shared private projects before they even reach out — no back-and-forth needed.

If you’re job hunting with a gitea.com account or self-hosted repos, this is one of the easiest workflow upgrades you can make. No need for GitHub or sacrificing your self-hostedness.

“But I’m Giving OAuth Access to a Third Party…”

Fair concern — as a self-hoster you should be skeptical. ShareMyGit requests read-only access to your repositories. It doesn’t clone or mirror your code anywhere. Your repos stay on your server, and the share link simply lets a viewer browse through ShareMyGit’s interface.

If you ever want to cut access, just revoke the OAuth application on your instance and all share links stop working immediately. You stay in control.

Final Thoughts

Recruiters don’t need full access — they just need to see your code. ShareMyGit gives you a fast, secure way to do that:

• No visibility changes while you’re applying for jobs
• No extra accounts or repo invites
• No infrastructure exposure
• No zip-file sending

Generate a link, send it, done. 🚀