-
Notifications
You must be signed in to change notification settings - Fork 29.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New git welcome missing guide #140293
New git welcome missing guide #140293
Conversation
I think it's misleading to start with the sentence "Source control depends on Git being installed." and only in the final paragraph mention that other providers exist. I suggest starting with "Source control tracks code changes to look back and revert." Next: "Git is the most popular... ...easy to learn and use." Next: "This built-in source control depends on Git being installed on your workstation." Next, the download button and the reload instruction. Finally: "Other source control providers exist and can be installed from the Marketplace." |
Thank you for the feedback! I see how the explainer-first flow can be a good alternative. I preferred to keep the action first to avoid burying the lede.
The current view for "missing git" starts in a similar fashion, focused on git:
The main reason for git focus is that we have more users on git vs the much smaller portion on the other providers. As this view also targets SCM beginners, users that are on other providers presumably don't need the additional onboarding that this view provides. |
Personally I'd try to trim down the text to something that's easier to read and has links to documentation that can help users get started:
|
+1 for the shorter text that has been suggested by @misolori. |
This PR applies the new
git.missing
welcome views from #136408.The new UI is behind an experiment setting, so we can test its impact and also explore other installations like terminal-based flows.
Initial commit for reference: