this post was submitted on 25 Oct 2023
293 points (97.7% liked)
Programmer Humor
32473 readers
558 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
Mmm yes number go up.
Progress.
Isn't it easier to delete the release? Unless they have no permission to do it I guess
It's a bit trickier since that is a neovim plugin so a bunch of people will automatically have updated to this tag using their plugin manager. Removing it will probably just make it worse.
I forgot the many plugin managers that download stuff directly from github. That makes way more sense.
How do you accidentally force push lol
I assume the accident was not to force push, but to the wrong branch
I hope they learned the value of protecting your branches.
This is why I always git push origin +branch_name
My go-to these days is to push the current branch, dynamically.
git push origin HEAD
Depending on the VC, HEAD has different prefix/suffixes to make it work.
Edit: formatting, also I never checkout master I do origin/master so I cannot even push it with this method. I think
I was wondering the same. Any branch that has any logic besides a ci build attached to it should have been force push protected by default...
Git rebase makes it possible getting used to do so
You guys actually release stuff?
But why is it a major number?
How do they get the numbering system? Is it automatic somehow?
Pretty sure they just type it in manually. See named tags in git.