Create git guides for beginners

[digitarald]

Why: The current version-control page is just a generic overview, slightly flavored with git. The github docs is also more a of UI and feature tour. Both assume git knowledge.

What: Beginner-focused content should walk through specific use cases that developers struggle with. By sticking to UI-based flows, those pages can lower the steep learning curve that most git guides have.

How: We'll add a new top-level /git docs category with a handful of short scenario-based articles. Anything that new developers need help with can be considered, prioritizing topics that cover most common use cases and pitfalls.

🚧 Draft ideas for topics, to be discussed:

1. Track and commit changed files
2. Resolving merge conflict
3. Checkout a remote branch
4. Create a github pull requests
5. FAQ for misc details

TBD:

• Brainstorm initial topics and converge on a shortlist
• Outline for top 3
• Create articles (2 pager)

What git issues do developers struggle with most?

Search results on google are probably more driven by frustration than importance/frequency of the use case.

cc @burkeholland @ItalyPaleAle @sana-ajani

[ItalyPaleAle]

Is this something we could work on with support for someone at GitHub? Like someone in Martin's team?

And do you think our docs would be a good place to also explain the why of Git, in addition to the how ?

[digitarald]

@ItalyPaleAle yes and yes (especially for use cases, so they make sense to their audience). Let's sync next year to pull in the right people to help write & review.

[nelsonmic]

hi @digitarald, I would like to help out with this, please can you help me get started?

[AriESQ]

This seems out of scope for VS-Code documentation. There is actually good reason to be intentional about keeping a conceptually clear boundary between GitHub features, Git, and VS-Code /(web).

[gregvanl]

Closing issue as not on any current milestone plan. We can reopen the issue when the work is resourced and scheduled.