We lost 3800 stars on Github in 1 click đ
Never switch public repository to private
Our team leaked an API key in a Git commit during maintenance and was immediately alerted by GitGuardian. To revert that change and clean up the git history, Pierre decided to switch our repository from public to private until our team fixed it. Never do that! We just lost all the stars and the forks of our repo when switching back to public đ.
The Github support
Well, we desperately tried to contact GitHub support. And we receive this response...
Please, help us!
We face an unusual situation, and we ask for your help! There are two ways of helping:
- I am sure Github can do something about that, but they don't want to bother. Can you share this story with your friends working at Github? If someone working there can help, they can contact us via hello {at} qovery {dot} com. I will send you a super Qovery swag pack with a great bottle of French red wine đ· (I promise it will be excellent!).
- If you like what we are doing at Qovery - please give us a star âïž. You can read this Reddit post when I announced the open-source launch of our Qovery Engine.
I hope this post will help you never make the same error as we did!
---
Update on the 6th of December 2021
The community is lovely đ€© Thank you all for your fantastic support. We received support from people all around the world. It is crazy. Thank you, thank you, thank you. We almost reached 1k stars again - please keep supporting us with a star âïž. GitHub is also considering this incident, and I feel they tried their best to solve our issue.
.svg)
.svg)
.svg)
Suggested articles
Stop fighting cluster sprawl. Learn why traditional scripting and GitOps fail at scale, and discover how to achieve fleet-wide consistency without the complexity of Kubernetes Federation.
Looking to automate your Kubernetes environment in 2026? Discover the top automation tools, their weaknesses, and why scaling your infrastructure requires a unified management platform.
As the AI race shifts from hardware acquisition to GPU utilization, success is now an orchestration problem. Learn how to bridge the 84% capacity gap, eliminate "ghost" expenses, and leverage AI infrastructure copilots to maximize ROI in 2026.
Is Kubernetes complexity killing your teamâs velocity? Compare Docker vs. Kubernetes in 2026 and discover how to get production-grade orchestration with the "Git Push" simplicity of Docker.
Comparing VMware Tanzu vs. Red Hat OpenShift for enterprise Kubernetes? Explore their features, pros, cons, and discover why Qovery is the smarter alternative for rapid application delivery.
.webp)