programmerhumorยทProgrammer Humorby๐จ๐๐ค๐๐๐ย We've all been thereView original on feddit.de281Comments16Reply
sshotgun_crabย lemmy.world2Hide 2 repliesIsn't it easier to delete the release? Unless they have no permission to do it I guess17Reply
๐จ๐๐ค๐๐๐ย replyfeddit.de1Hide 1 replyIt'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.14Reply
sshotgun_crabย replylemmy.worldI forgot the many plugin managers that download stuff directly from github. That makes way more sense.7Reply
๐จ๐๐ค๐๐๐ย replyfeddit.de3Hide 3 repliesI assume the accident was not to force push, but to the wrong branch18Reply
mmagic_lobster_partyย replykbin.socialI hope they learned the value of protecting your branches.12Reply
fforgedditย replysopuli.xyzMy 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 think1Reply
DacoTacoย replylemmy.worldI 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...7Reply
promitheasย iusearchlinux.fyi1Hide 1 replyHow do they get the numbering system? Is it automatic somehow?2Reply
16 replies
yep, lol
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_nameMy 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.