<font color="#993300">Uh oh @David263, something went wrong! I wasn't expecting this change. Please go over the instructions again and make sure you've followed them as exactly as you can. If this is a pull request, you might close it so you can start fresh. Keep trying, you'll get there! If you would like assistance troubleshooting the issue you are encountering, create a post on the GitHub Community board. You might also want to search for your issue to see if other people have resolved it in the past<br>d<br><br><font size="3">II have no idea what went wrong. I thought I followed the instructions. I hate these courses--so complicated, and you can't tell what is going on from these diagrams with circles and labels.</font><br></font>
I’m sorry it’s such a challenge, @david263. Git can be very difficult to learn so I certainly understand the frustration. What course are you receiving this message in? You can also drop a link to the page in which you’re seeing this and I’d be glad to take a look.
Sorry, I was so frustrated I didn’t take the time to note which of the 3 or 4 courses I have tried produced this error message. I don’t know how to find it again.
I have only completed one of the courses I tried; the rest are abandoned. It just gets so complicated with all the steps that I don’t fully understand. I can understand the basic workflow of finding a file, changing it, then either requesting a review or requesting that it be pulled into the master branch, but everything beyond that gets me lost, especially the complex merging scenarios.
I didn’t have this level of difficulty when learning professional source control systems when I worked as a software engineer, but git seems to be harder to learn than most other aspects of modern software development.
I don’t see why git has to be so complicated or why the tutorials are so insufficient in explaining each basic concept (what is a branch, what is a version, what is a review, what is a pull, etc., and how to do each one).
And then doing local development using git or GitHub Desktop is another level of complexity that is not well explained. If I’m to contribute to open software, I want to be able to do local development and building using the interactive tools I already use (editor, browser, …).
Thanks for the feedback, @david263. The Git specific items you mention bring to mind a series of videos @brianamarie completed. They’re on YouTube, hopefully they answer some of the questions you’ve had.
I watched all of them a week ago, some twice, and they helped a little, but they had the same problems for me as other tutorials: they were either obvious or impossible to understand (they are all way too short). I have a feeling that I will have to learn by doing. But I’m not sure I’m even up for it.
For example, I would like to implement bug fixes for products I use all the time, such as Firefox and Thunderbird, but I’m guessing that trying to get the build working on my computer will be a nightmare of dependencies, learning various programming languages and build tools, and impossibly long build times. And I’m not sure that the files and dependencies will fit into a reasonable size (say, 1 GB) on my ordinary desktop computer.
Maybe I’m just being negative, but the truth is that I’ve learned a lot about local git operations and remote GitHub operations and I’m overwhelmed by the complexity. I can’t see using this stuff for actually changing more than just a line or two of code in an independent/orthogonal area of a product.
I’ve spent several weeks on git and GitHub, watching and working through tutorials, and unless I find better tutorials I’ve decided to move on. It’s just too unpleasant. I have so much more that I want to learn before I can feel that I have a good idea of the Web technology that has come out in the past few years while I’ve been working on specific projects. And I really have to get back to my projects, which have been idle all this time.