fflauschke feddit.de2Hide 2 repliesFYI you should be able to disallow directly pushing to the master branch and only allow merging43
VVanillaGorilla replykbin.socialBut that happened to most of us I'd wager, so you're at least not alone.6
PPrimarily0617 kbin.socialwhy on earth would you have a direct main CD pipeline without proper protections against pushing straight to that branch?4
BBruceDoh sh.itjust.worksBut surely you can just revert it, no big deal. Unless you have CI/CD pipelines on an unprotected branch...2
digitallyfree kbin.socialYou didn't just push it to main, you also pushed confidential code to the public repo!2
ssiriusmart feddit.ukyou mean master? github changed the default branch name from master to main during black history month or something, i think its complete nonsense0
FYI you should be able to disallow directly pushing to the master branch and only allow merging
That's exactly what a not stupid person would do
But that happened to most of us I'd wager, so you're at least not alone.
And this is why you always immediately turn on branch protection.
Who needs "Read-only Friday" anyways, right?
Fuck, there goes the weekend 🤦.
That sounds like a Monday problem
why on earth would you have a direct main CD pipeline without proper protections against pushing straight to that branch?
This is my I never let let my prod pipelines run builds automatically.
Oh fuck. Hang on to your pooper.
But surely you can just revert it, no big deal. Unless you have CI/CD pipelines on an unprotected branch...
@NicKoehler
lol, been there, got the t-shirt.
To your own personal repository, right?!
That's the neat part, no
You didn't just push it to main, you also pushed confidential code to the public repo!
No please, let’s get the grammar right on this meme here on Lemmy
So, do you have automatic deployments or?
you mean master? github changed the default branch name from master to main during black history month or something, i think its complete nonsense