Your GitHub is your portfolio
Gitog — 1 week reflection after launch 🚀
One week ago, I launched Gitog, a tool that turns GitHub projects into a developer portfolio.
I built the MVP in one week and launched it quickly to get feedback.
The response was encouraging, but I quickly realized something was missing: I had focused too much on shipping and moved away from the original problem I wanted to solve.
Why I built Gitog
I created Gitog because I experienced this problem myself.
When recruiters asked for my portfolio, I often had nothing ready, or I had to send my GitHub profile and multiple project links one by one.
It worked, but it wasn’t the best way to present my work.
What changed
So I spent the last week rebuilding Gitog around this core idea:
Helping developers create a clean portfolio from their GitHub projects in minutes.
Based on the feedback I received, I redesigned the interface, improved the user experience, and fixed many things that were missing.
What’s next
Gitog will never be perfect and it won’t fit everyone, but the goal is simple:
Help developers quickly showcase their work.
Thanks again to everyone who shared feedback. Building alone makes it easy to miss things, and your suggestions helped shape the product.
I’ll keep improving it step by step.
Private repository support is also on my roadmap.
Try Gitog: https://gitog.net/
Congrats on the relaunch. One thing I immediately wondered about is whether developers will know which projects actually strengthen their portfolio versus simply displaying everything from GitHub. A portfolio isn't just a collection of repositories, it's a story about capability. If Gitog can help developers understand what recruiters are likely to notice first, that becomes a much stronger value proposition than simply turning GitHub projects into a portfolio.
I specialize in independent product validation for early-stage SaaS. I evaluate products from a genuine first-time user's perspective, uncover where trust, clarity, or usability break down, and produce professional walkthrough videos alongside structured findings that founders can use to improve onboarding, product adoption, and marketing.
Thanks for your feedback! I completely agree with your point. A portfolio is not just about displaying repositories, it’s about highlighting the right projects and telling a story about your skills. Gitog is still at an early stage, so I’m still learning what developers and recruiters value the most. I think understanding which projects people choose to showcase will be a very interesting direction to explore. Thanks again for sharing this insight, it’s definitely something I’ll keep in mind as Gitog evolves.
Glad it resonated. I think that's one of those patterns that only becomes obvious after watching real developers build portfolios over time. I will be interested to see how Gitog evolves as you gather more of that data. Looking forward to seeing where you take it.
Thanks, I really appreciate it!
I agree, I think the best insights will come from real usage and seeing how developers actually present their work.
Gitog is still at an early stage, so I’m excited to learn from users and keep improving it step by step.Thanks again , I’ll keep sharing the progress!
I like that the biggest lesson after launch wasn't about adding features—it was realizing you'd drifted away from the original problem you wanted to solve.
I'll be interested to see which projects developers consistently choose to highlight first. Those patterns often reveal what recruiters actually look for rather than what developers assume they value.
Thanks for your feedback! You’re right, it’s a really interesting idea. The project is still at an early stage, so I don’t have enough data yet to really know those patterns, but I’ll definitely keep an eye on it. Thanks again for your insight. I’ll probably continue sharing the progress and my thoughts here on Indie Hackers.
Makes sense.
The early stage is actually when those patterns are most useful to observe. Often the first few users reveal what the product is really helping them communicate, not just what you originally intended.
That's a great point. Thanks again for your insights!
Appreciate the question.
The answer depends on the role you want that awareness to play in the product, and I don't think I'd do it justice in a few comments.
Would be good to discuss it in the context of what you're building.
What's the best email to reach you on?
Thanks! You can reach me at supportgitog@gmail.com.
Thanks! I’ve just sent it over.
Looking forward to hearing your thoughts whenever you have a chance.