News for hackers. Stuff that matters.
Re:Beej's Guide to Git by globular-toast on Wednesday February 05, 2025 @02:54AM (#42945358)
I highly doubt tortoise or any tool can "break" a repo. This might be a sign that you don't understand git either. Now I'm sure it can lead to people who don't know what they're doing doing the wrong thing, but if they're allowed to push somewhere and make it someone else's problem, that's not their fault. They've been forced to use git, so there should be someone else who actually understands git.
Re:Beej's Guide to Git by _puk on Wednesday February 05, 2025 @03:31AM (#42945665)
Ah, we're holding it wrong. Got it.
Re:Beej's Guide to Git by wruza on Wednesday February 05, 2025 @09:42AM (#42949114)
“Break” doesn’t mean repo integrity corruption. It means that you try to merge a branch, and it shits itself with hundreds of conflicts that shouldn’t appear and/or has changes that may partially revert the progress made by other merges.

if they're allowed to push somewhere and make it someone else's problem, that's not their fault

What? This made zeroest sense of the day. Like, I should walk to their desk and check if a feature branch is okay to push or what?

Re:Beej's Guide to Git by globular-toast on Wednesday February 05, 2025 @10:45AM (#42950162)
Usually people make pull requests.
Re:Beej's Guide to Git by wruza on Wednesday February 05, 2025 @11:01AM (#42950428)
Yep, with a branch they pushed into. I guess you're ignoring the same context as another commenter elsewhere, probably because your workflow is restricted only to modes that git "supports".