FYI you should be able to disallow directly pushing to the master branch and only allow merging
32 0 ReplyThat's exactly what a not stupid person would do
15 0 ReplyBut that happened to most of us I'd wager, so you're at least not alone.
3 0 Reply
And this is why you always immediately turn on branch protection.
7 0 ReplyWho needs "Read-only Friday" anyways, right?
6 0 ReplyFuck, there goes the weekend 🤦.
5 0 ReplyOh fuck. Hang on to your pooper.
4 0 ReplyThat sounds like a Monday problem
4 0 Replywhy on earth would you have a direct main CD pipeline without proper protections against pushing straight to that branch?
3 0 ReplySo, do you have automatic deployments or?
2 0 ReplyThis is my I never let let my prod pipelines run builds automatically.
2 0 Replylol, been there, got the t-shirt.
2 0 ReplyTo your own personal repository, right?!
2 0 ReplyThat's the neat part, no
5 0 Reply
But surely you can just revert it, no big deal. Unless you have CI/CD pipelines on an unprotected branch...
2 0 ReplyYou didn't just push it to main, you also pushed confidential code to the public repo!
1 0 Replyyou mean master? github changed the default branch name from master to main during black history month or something, i think its complete nonsense
1 0 Replyfor that i always change my master branch name back to master
1 0 Reply