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
Build Your Own PaaS: Stop depending on fixed cloud offerings. Discover the top 8 tools, including Qovery, Dokku, and Cloud Foundry, that let you build a customizable, low-maintenance PaaS on your cloud infrastructure.
Simplify Kubernetes Deployment. Learn the difficult 6-step manual process for deploying Docker containers to Kubernetes, the friction of YAML and kubectl, and how platform tools like Qovery automate the entire workflow.
Observability in DevOps: Diagnose system failures faster. Learn how true observability differs from traditional monitoring. End context-switching, reduce MTTR, and resolve unforeseen issues quickly.
Integrate security seamlessly into your CI/CD pipeline. Learn the 6 best DevSecOps practicesâfrom Policy as Code to continuous monitoringâand see how Qovery automates compliance and protection without slowing development.
Fed up of rising Heroku costs and frequent outages? This guide compares the top 10 Heroku alternatives and competitors based on features, pricing, pros, and consâhelping developers and tech leaders choose the right PaaS.
Provisioning cloud resources shouldnât require a second stack of tools. With Qoveryâs new Terraform and OpenTofu support, you can now define and deploy your infrastructure right alongside your applications. Declaratively, securely, and in one place. No external runners. No glue code. No tool sprawl.
Looking for a Flux CD alternative? Discover why Qovery stands out as the #1 choice. Compare features, pros, and cons of the top 10 platforms to simplify your deployment strategy and empower your team.
.webp)