That's what I do too. I'm amazed at how fast it is to find solutions at the source.
GitHub issues are great to find workarounds, possible things one might be doing wrong, or the issue might have been fixed in a later version and we just didn't update to it.
I have also started scouring the original documentation whenever I hit an issue, they usually have common issues documented and how to solve them.
I think these are really the next steps after Google in improving research and solution finding.
Excellent advice, Tiger. Especially on research and focus.
In my Solve Problems like a Developer post, I explained how I use Google as a last resort when solving a problem.
The other day we ran into issues with Handsontable - a JS library for working with Excel-like tables. Some of the callbacks didn't want to work as we expected.
Someone had already jumped at Google, and after 30 or so minutes of no luck, I asked if they checked the Github of the project, and boom, there was the answer.
I still feel people give too much credibility to Google and forget things like searching GitHub repository issues when a particular library doesn't work.