FYI you should be able to disallow directly pushing to the master branch and only allow merging
this post was submitted on 23 Jun 2023
138 points (97.9% liked)
Programmer Humor
32461 readers
433 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
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?
That sounds like a Monday problem
Fuck, there goes the weekend 🤦.
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?
This is my I never let let my prod pipelines run builds automatically.
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
But surely you can just revert it, no big deal. Unless you have CI/CD pipelines on an unprotected branch...
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?
view more: next ›