Add links to Git Bash resources for troubleshooting GitHub Docs tutorials

[jlduchaney]

Code of Conduct

• I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?

https://docs.github.com/en/get-started/exploring-projects-on-github/contributing-to-a-project

What part(s) of the article would you like to see updated?

I'm on the "Creating a branch to work on" step. When I try to follow the instructions, Git Bash says, "fatal: not a valid object name: 'master'". Since the article provides no guidance on troubleshooting Git Bash, the reader's left stranded at a dead end.

Can you please add links for where users can go for any Git Bash errors they might encounter in this tutorial?

Additional information

I'm teaching myself how to code and was referred to GitHub Docs via MDN Learning Area/Guides. Contributing to a project is the third out of five links they recommend in their Git and GitHub article.

Since I suspect many other learners are arriving at this tutorial in the same way, it might be helpful to note whether any prior Git Bash knowledge is prerequisite to successfully complete the steps (via the above recommended solution).

[welcome]

Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[nguyenalex836]

@jlduchaney Thank you for raising this issue! I'll get this triaged for review ✨ Our team will provide feedback regarding the best next steps for this issue - thanks for your patience! 💛

[nguyenalex836]

@jlduchaney Thank you for your patience while our team reviewed!

I appreciate this is frustrating and I’m sorry you’ve had that experience. Generally we take an “opinionated” approach when it comes to the docs content, so we’ll always focus on the core experience, and in this case, that’s the “GitHub flow“. As we can’t be sure how the Git Bash experience will change and it’s not our product, it isn’t something we can help with at this time 💛

What I will say is that we’re aware we need to address some issues in the “Getting started” content as a whole, and I’ll make a note of your feedback in the internal conversations around that initiative.