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
At enterprise scale, managing provider-specific Kubernetes YAML across multiple clouds creates crippling configuration drift and operational toil. By adopting an agentic Kubernetes management platform, infrastructure teams abstract cloud-specific configurations (like ingress controllers and storage classes) into a single, declarative intent that automatically reconciles across 1,000+ clusters.
To stop GPU costs from destroying SaaS margins, teams must transition from static to consumption-based infrastructure by utilizing Karpenter for dynamic provisioning, maximizing hardware density with NVIDIA MIG, and leveraging Qovery to tie scaling directly to business metrics.
AI is helping developers write more code, faster than ever. But writing code is only half the story. What happens after? Building, deploying, debugging, scaling. That's where teams still lose hours.We're building Qovery for this era. Not just to deploy your code, but to make everything that comes after writing it just as fast.
By adopting GitOps and utilizing management platforms like Qovery, fintech teams can automatically generate DORA-compliant audit trails, transforming regulatory compliance from a manual, time-consuming chore into an automated, native byproduct of their infrastructure.
Kubernetes success is determined by Day 2 execution, not Day 1 deployment. While migration is a bounded project, maintenance is an infinite loop that often consumes 40% of senior engineering capacity. To protect margins and velocity, enterprises must transition from manual toil to agentic automation that handles scaling, security, and cost.
Day-0 is planning, Day-1 is deployment, and Day-2 is the infinite lifecycle of maintenance. While Day-0/1 are foundational, Day-2 is where enterprise operational debt accumulates. At fleet scale (1,000+ clusters), managing these differences manually is impossible, requiring agentic automation to maintain stability and eliminate toil.
.webp)