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
Oh fuck. Hang on to your pooper.
why on earth would you have a direct main CD pipeline without proper protections against pushing straight to that branch?
You didn’t just push it to main, you also pushed confidential code to the public repo!
To your own personal repository, right?!
That’s the neat part, no
lol, been there, got the t-shirt.
This is my I never let let my prod pipelines run builds automatically.
But surely you can just revert it, no big deal. Unless you have CI/CD pipelines on an unprotected branch…
Where are the tests? Pushing to main (“trunk based development”) is a great workflow if you have those
you mean master? github changed the default branch name from master to main during black history month or something, i think its complete nonsense
for that i always change my master branch name back to master
So, do you have automatic deployments or?
