Comment by 1over137
2 days ago
We’re not all working at $bigcorp with dedicated help teams. Sites like this are great and have helped me many times!
2 days ago
We’re not all working at $bigcorp with dedicated help teams. Sites like this are great and have helped me many times!
What happens when you are the help team and it's the first time something goes wrong?
A 'team', by definition, consists of more people than 'you.'
And, by the time a '#githelp team' is formed, it's to address patterns to which there are known solutions.
One of the many problems with Git, is that these solutions depend very, very much on the structure of the repo and the common practices of its users.
So, instead of executing random commands from the Internet, just ask. Please! Or, if there's truly nobody going to be around, give in and recreate the repo. You'll save yourself so much pain in the long run...
> A 'team', by definition, consists of more people than 'you.'
I'm the resident git expert, but not by choice. There's more that I don't know than that I do. It's not uncommon that I need to use internet recipes to un-wedge someone's clone.
> Or, if there's truly nobody going to be around, give in and recreate the repo. You'll save yourself so much pain in the long run...
This is insane. There are a dozen other people using the remote, not to mention a whole CI/CD build configuration.
OK, so you've truly screwed up your your personal/small-team repos to the point of requiring poorly-understood command sequences from the Notoriously Reliable Internet more than once?
I applaud you for your honesty, but... Really?
I don't understand your surprise or disbelief. I would imagine most devs have been there. As evidence: just look at Stack Overflow, and compare it to what it's apparently intended to look like and how it's supposed to work (as a denizen of meta.stackoverflow.com I am quite familiar with this struggle).
Bro, really, self-taught people with a bare minimum understanding of the tools they use are super normal, and when they get into a pit they have to fix it themselves.
Although to your point folks would be better served carefully reading the docs / git book than googling a specific solution to their specific error code.
For me, the value of things like this is in learning the terminology for what I broke and how to fix it. I'm not going to copy-and-paste advice off the Internet. I never have. It's still super helpful to see "oh, that thing I want to do is called frobnitzing the corple. Now I know what to Google!"
[flagged]
13 replies →
Yes. I think the ratio of small-team repos this describes is close to 100%. You seem to have a certain idea of how repos are managed. I don't think it's very representative of reality.