From b936b72d124b25a8cebb1cdec405c0edb3f9af9f Mon Sep 17 00:00:00 2001 From: Harald Kirschner Date: Mon, 3 Oct 2022 10:34:06 -0700 Subject: [PATCH 1/8] First toc --- docs/sourcecontrol/intro-to-git.md | 33 ++++++++++++++++++++++++++++++ 1 file changed, 33 insertions(+) create mode 100644 docs/sourcecontrol/intro-to-git.md diff --git a/docs/sourcecontrol/intro-to-git.md b/docs/sourcecontrol/intro-to-git.md new file mode 100644 index 0000000000..4ed19285a4 --- /dev/null +++ b/docs/sourcecontrol/intro-to-git.md @@ -0,0 +1,33 @@ +# Intro Git in Visual Studio Git + +## What is Git? + +- Keep track of changes to code +- Synchronize code between different people +- Iterate on code and test ideas without losing the original +- Revert back to old versions of code + +## Using a Git GUI like VS Code vs CLI + +- Faster to learn. +- Faster feedback. +- Quicker to solve problems. +- Mix both to work faster. + +# Installing Git + +# Your first Git repository + +## Pull a repository from GitHub + +## Initialize a local repo + +# Staging and committing code changes + +## Creating new files + +## Pushing changes to an upstream repository + +## Pulling changes from upstream + +# Branching \ No newline at end of file From 59b1bb724ff842201f36bc263cc28fb9e2e664ce Mon Sep 17 00:00:00 2001 From: Harald Kirschner Date: Mon, 12 Dec 2022 10:30:09 -0800 Subject: [PATCH 2/8] Draft --- docs/sourcecontrol/intro-to-git.md | 110 +++++++++++++++++++++++------ 1 file changed, 90 insertions(+), 20 deletions(-) diff --git a/docs/sourcecontrol/intro-to-git.md b/docs/sourcecontrol/intro-to-git.md index 4ed19285a4..b4c2303f3b 100644 --- a/docs/sourcecontrol/intro-to-git.md +++ b/docs/sourcecontrol/intro-to-git.md @@ -1,33 +1,103 @@ -# Intro Git in Visual Studio Git +# Intro Git in Visual Studio Code -## What is Git? +## Introduction +Git and GitHub are powerful tools for managing code, collaborating with others, and keeping track of changes to your codebase. Whether you're new to coding or a seasoned professional, learning how to set up Git and GitHub in VS Code is a valuable skill to have. -- Keep track of changes to code -- Synchronize code between different people -- Iterate on code and test ideas without losing the original -- Revert back to old versions of code +VS Code's intuitive UI makes it easy for beginners to understand and perform common Git actions, such as pulling from and pushing to a remote repository, creating and merging branches, and staging and committing code changes. For seasoned professional, the ability to perform Git actions directly in the editor saves time and effort compared to using the Terminal. The integrated nature of VS Code's Git features also allows for a seamless workflow, without the need to switch between the editor and the Terminal. -## Using a Git GUI like VS Code vs CLI +## Setup Git in VS Code -- Faster to learn. -- Faster feedback. -- Quicker to solve problems. -- Mix both to work faster. +To use Git and GitHub in VS Code, first make sure you have Git installed on your computer. If Git is missing the *Source Control* tab will show instructions on how to install it. Make sure to restart VS Code afterwards. -# Installing Git +(Todo: Clarify authentication setup for GitHub from within VS Code) -# Your first Git repository +## Open a Git repository -## Pull a repository from GitHub +VS Code provides several ways to get started in a Git repository. -## Initialize a local repo +### Clone a repository from GitHub -# Staging and committing code changes +To clone a repository from GitHub, execute the `Git: Clone` command or click the `Clone Repository` button in the *Source Control* view. If you clone from GitHub, VS Code will prompt you to authenticate with GitHub. This will allow you to search all available repositories and clone private repositories. For other Git providers enter the repository URL and click "Clone" and pick a folder. VS Code will open it once the repository has been cloned. -## Creating new files +### Initialize a repository in a local folder +To initialize a new local repository, pick an existing or new folder on your computer and open it in VS Code. In the "Source Control" tab, click the "Initialize Repository" button. This will create a new Git repository in the current folder, allowing you to start tracking code changes. -## Pushing changes to an upstream repository +#### Publish local repository to GitHub -## Pulling changes from upstream +Once you have a local Git repository set up, you can publish it to GitHub. This will create a new repository on your GitHub account, and push your local code to the remote repository. It is great for backing up your code, collaborating with others, and automating your workflow with GitHub Actions. -# Branching \ No newline at end of file +Use the the `Publish to GitHub` command or the "Publish Repository" button in the "Source Control" tab. This will prompt you to authenticate with GitHub. You can then choose a name and description for the repository, and whether to make it public or private. Once the repository has been created, VS Code will push your local code to the remote repository. + +### Open a GitHub repository in a Codespace + +Codespaces let you to open a GitHub repository in a full configured cloud-based development environment, allowing you to develop in a browser without having to install any software on your local computer. They include free usage for individuals which makes it easy to getting started in open source. + +Install the [GitHub Codespaces](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) extension into VS Code and sign in with GitHub. Run the `Codespaces: Create New Codespace` command and pick the repository and branch you want to open. The Codespace will open in a new window. + +(Todo: Add video loop) + +Alternatively, you can also start from a template from the [GitHub's Codespaces site](https://github.com/codespaces/templates). If you already have a Codespace open in your browser, you can open it in your Desktop VS Code by running the `Codespaces: Open in VS Code Desktop` command. Learn more about Codespaces to forwarding ports. + +### Open a GitHub Repository remotely + +VS Code remote repositories allows you to browse and edit a GitHub repository without cloning it to your local computer. This is useful for quickly making changes to a remote repository without having to clone the entire codebase to your local machine. + +First install the the [GitHub Repositories](https://marketplace.visualstudio.com/items?itemName=GitHub.remotehub) extension. Run the command `Remote Repositories: Open Remote Repository...` or use the `Open Remote Repository` button the Explorer view. Search and select the GitHub repository that you want to open. + +(Todo: Add screenshot) + +Browse, search, and edit files as you would in a local repository. Commit from the *Source Control* will go directly be integrated to the remote repository. The remote repository can not execute any code or run terminal commands. + +(Todo: Link to further docs on remote repositories) + +## Staging and committing code changes + +Once you have a Git repository set up, you can start tracking code changes by staging and committing your newly created and edited code. + +Tip: Commit early and often. This will make it easier to revert to previous versions of your code if needed. + +(Todo: Add screenshot for staging and committing) + +To stage a file, click the "plus" icon next to the file in the "Source Control" tab. This will add the file to the "Staged Changes" section, indicating that it will be included in the next commit. Staged changes can also be discarded by clicking the "minus" icon next to the file. + +To commit your staged changes, type a commit message and click the "Commit" button. This will save your changes to the local Git repository, allowing you to revert to previous versions of your code if needed. All file changes and commits are shown in the "Timeline" section. + +(Todo: Add screenshot for timeline) + +## Pushing and pulling remote changes + +Once you have made commits to your local Git repository, you can push them to the remote repository. The "Sync" button will indicate how many commits are going to be pushed and pulled. Clicking "Sync" button will download (pull) any new remote commits and upload (push) new local commits to the remote repository. + +(todo: Add screenshot for sync) + +> Tip: Make sure to enable `Git: Autofetch` to always get an up-to-date remote commit indicators. + + Push and pull can also be performed individually by using their respective commands. + +## Using branches + +In Git, branches allow you to work on multiple versions of your codebase simultaneously. This is useful for experimenting with new features or making large code changes without affecting the main codebase. + +(todo: Add screenshot for branch indicator) + +The branch indicator in the status bar shows the current branch and lets you switch to new and existing branches. To create a new branch, click the branch indicator and choose to create it from the current branch or another local one. Type a name for the new branch, and confirm. This will create a new branch and switch you to it, allowing you to make changes to your code without affecting the main branch. + +> Tip: If you use the GitHub Pull Request extension you can create a branch directly from an issue, which get you started coding in a new new local branch and automatically prefill the pull request for you. + +To push the branch to the remote repository, click "Publish" in the "Source Control" tab. This will create a new branch on the remote repository, allowing you to collaborate with others on the branch. + +## Merging branches and changes + +(Maybe: Lacks primary UI) + +### Creating and reviewing GitHub Pull Requests + +In Git and GitHub, Pull Requests (PRs) are a way for collaborators to review and merge code changes from separate branches into the main branch. This allows teams to review and approve code changes before they are incorporated into the main codebase, ensuring that only high-quality code is merged. + +To use Pull Requests in VS Code, you will need to install the [GitHub Pull Request & Issues](https://marketplace.visualstudio.com/items?itemName=GitHub.vscode-pull-request-github) extension. This extension adds PR and issue tracking functionality to VS Code, allowing you to create, review, and merge PRs from within the editor. + +To create a PR, make sure you are on a separate branch from the main branch, and push your code changes to the remote repository. In the "Source Control" tab, click the "Create Pull Request" button. This will open the PR creation form, where you can enter a title and description for the PR, and choose which branch to merge the changes into. Click "Create" to create the PR. + +To review a PR, click the "Review Pull Request" button in the "Source Control" tab, and select the PR you want to review. This will open the PR in a new editor window, where you can review the code changes and leave comments. Once you are satisfied with the code changes, you can click the "Merge" button to merge the PR into the main branch. + +Learn more about Pull Requests in the [VS Code's GitHub documentation](https://code.visualstudio.com/docs/sourcecontrol/github). \ No newline at end of file From 1e6d8f992417b85f0fd61a4aa02ca22c36397e5a Mon Sep 17 00:00:00 2001 From: Harald Kirschner Date: Mon, 12 Dec 2022 10:50:46 -0800 Subject: [PATCH 3/8] First round of edits --- docs/sourcecontrol/intro-to-git.md | 35 ++++++++++++++---------------- 1 file changed, 16 insertions(+), 19 deletions(-) diff --git a/docs/sourcecontrol/intro-to-git.md b/docs/sourcecontrol/intro-to-git.md index b4c2303f3b..d64dd07c5e 100644 --- a/docs/sourcecontrol/intro-to-git.md +++ b/docs/sourcecontrol/intro-to-git.md @@ -15,34 +15,35 @@ To use Git and GitHub in VS Code, first make sure you have Git installed on your VS Code provides several ways to get started in a Git repository. -### Clone a repository from GitHub +### Clone a repository -To clone a repository from GitHub, execute the `Git: Clone` command or click the `Clone Repository` button in the *Source Control* view. If you clone from GitHub, VS Code will prompt you to authenticate with GitHub. This will allow you to search all available repositories and clone private repositories. For other Git providers enter the repository URL and click "Clone" and pick a folder. VS Code will open it once the repository has been cloned. +To clone a repository from GitHub, execute the **Git: Clone** command or select the **Clone Repository** button in the **Source Control** view. If you clone from GitHub, VS Code will prompt you to authenticate with GitHub. This will allow you to search all available repositories and clone private repositories. For other Git providers enter the repository URL and select **Clone** and pick a folder. VS Code will open it once the repository has been cloned. ### Initialize a repository in a local folder -To initialize a new local repository, pick an existing or new folder on your computer and open it in VS Code. In the "Source Control" tab, click the "Initialize Repository" button. This will create a new Git repository in the current folder, allowing you to start tracking code changes. + +To initialize a new local repository, pick an existing or new folder on your computer and open it in VS Code. In the **Source Control** tab, select the **Initialize Repository** button. This will create a new Git repository in the current folder, allowing you to start tracking code changes. #### Publish local repository to GitHub Once you have a local Git repository set up, you can publish it to GitHub. This will create a new repository on your GitHub account, and push your local code to the remote repository. It is great for backing up your code, collaborating with others, and automating your workflow with GitHub Actions. -Use the the `Publish to GitHub` command or the "Publish Repository" button in the "Source Control" tab. This will prompt you to authenticate with GitHub. You can then choose a name and description for the repository, and whether to make it public or private. Once the repository has been created, VS Code will push your local code to the remote repository. +Use the **Publish to GitHub** command or the **Publish Repository** button in the **Source Control** tab. This will prompt you to authenticate with GitHub. You can then choose a name and description for the repository, and whether to make it public or private. Once the repository has been created, VS Code will push your local code to the remote repository. ### Open a GitHub repository in a Codespace Codespaces let you to open a GitHub repository in a full configured cloud-based development environment, allowing you to develop in a browser without having to install any software on your local computer. They include free usage for individuals which makes it easy to getting started in open source. -Install the [GitHub Codespaces](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) extension into VS Code and sign in with GitHub. Run the `Codespaces: Create New Codespace` command and pick the repository and branch you want to open. The Codespace will open in a new window. +Install the [GitHub Codespaces](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) extension into VS Code and sign in with GitHub. Run the **Codespaces: Create New Codespace** command and pick the repository and branch you want to open. The Codespace will open in a new window. (Todo: Add video loop) -Alternatively, you can also start from a template from the [GitHub's Codespaces site](https://github.com/codespaces/templates). If you already have a Codespace open in your browser, you can open it in your Desktop VS Code by running the `Codespaces: Open in VS Code Desktop` command. Learn more about Codespaces to forwarding ports. +Alternatively, you can also start from a template from the [GitHub's Codespaces site](https://github.com/codespaces/templates). If you already have a Codespace open in your browser, you can open it in your Desktop VS Code by running the **Codespaces: Open in VS Code Desktop** command. Learn more about Codespaces to forwarding ports. ### Open a GitHub Repository remotely VS Code remote repositories allows you to browse and edit a GitHub repository without cloning it to your local computer. This is useful for quickly making changes to a remote repository without having to clone the entire codebase to your local machine. -First install the the [GitHub Repositories](https://marketplace.visualstudio.com/items?itemName=GitHub.remotehub) extension. Run the command `Remote Repositories: Open Remote Repository...` or use the `Open Remote Repository` button the Explorer view. Search and select the GitHub repository that you want to open. +First install the the [GitHub Repositories](https://marketplace.visualstudio.com/items?itemName=GitHub.remotehub) extension. Run the command **Remote Repositories: Open Remote Repository...** or use the **Open Remote Repository** button the Explorer view. Search and select the GitHub repository that you want to open. (Todo: Add screenshot) @@ -58,19 +59,19 @@ Tip: Commit early and often. This will make it easier to revert to previous vers (Todo: Add screenshot for staging and committing) -To stage a file, click the "plus" icon next to the file in the "Source Control" tab. This will add the file to the "Staged Changes" section, indicating that it will be included in the next commit. Staged changes can also be discarded by clicking the "minus" icon next to the file. +To stage a file, select the **+** (plus) icon next to the file in the **Source Control** tab. This will add the file to the **Staged Changes** section, indicating that it will be included in the next commit. Staged changes can also be discarded by selecting the **−** (minus) icon next to the file. -To commit your staged changes, type a commit message and click the "Commit" button. This will save your changes to the local Git repository, allowing you to revert to previous versions of your code if needed. All file changes and commits are shown in the "Timeline" section. +To commit your staged changes, type a commit message and select the **Commit** button. This will save your changes to the local Git repository, allowing you to revert to previous versions of your code if needed. All file changes and commits are shown in the **Timeline** section. (Todo: Add screenshot for timeline) ## Pushing and pulling remote changes -Once you have made commits to your local Git repository, you can push them to the remote repository. The "Sync" button will indicate how many commits are going to be pushed and pulled. Clicking "Sync" button will download (pull) any new remote commits and upload (push) new local commits to the remote repository. +Once you have made commits to your local Git repository, you can push them to the remote repository. The **Sync** button will indicate how many commits are going to be pushed and pulled. selecting **Sync** button will download (pull) any new remote commits and upload (push) new local commits to the remote repository. (todo: Add screenshot for sync) -> Tip: Make sure to enable `Git: Autofetch` to always get an up-to-date remote commit indicators. +> Tip: Make sure to enable **Git: Autofetch** to always get an up-to-date remote commit indicators. Push and pull can also be performed individually by using their respective commands. @@ -80,15 +81,11 @@ In Git, branches allow you to work on multiple versions of your codebase simulta (todo: Add screenshot for branch indicator) -The branch indicator in the status bar shows the current branch and lets you switch to new and existing branches. To create a new branch, click the branch indicator and choose to create it from the current branch or another local one. Type a name for the new branch, and confirm. This will create a new branch and switch you to it, allowing you to make changes to your code without affecting the main branch. +The branch dropdown in the status bar shows the current branch and lets you switch to new and existing branches. To create a new branch, select the branch indicator and choose to create it from the current branch or another local one. Type a name for the new branch, and confirm. This will create a new branch and switch you to it, allowing you to make changes to your code without affecting the main branch. > Tip: If you use the GitHub Pull Request extension you can create a branch directly from an issue, which get you started coding in a new new local branch and automatically prefill the pull request for you. -To push the branch to the remote repository, click "Publish" in the "Source Control" tab. This will create a new branch on the remote repository, allowing you to collaborate with others on the branch. - -## Merging branches and changes - -(Maybe: Lacks primary UI) +To push the branch to the remote repository, select **Publish** in the **Source Control** tab. This will create a new branch on the remote repository, allowing you to collaborate with others on the branch. ### Creating and reviewing GitHub Pull Requests @@ -96,8 +93,8 @@ In Git and GitHub, Pull Requests (PRs) are a way for collaborators to review and To use Pull Requests in VS Code, you will need to install the [GitHub Pull Request & Issues](https://marketplace.visualstudio.com/items?itemName=GitHub.vscode-pull-request-github) extension. This extension adds PR and issue tracking functionality to VS Code, allowing you to create, review, and merge PRs from within the editor. -To create a PR, make sure you are on a separate branch from the main branch, and push your code changes to the remote repository. In the "Source Control" tab, click the "Create Pull Request" button. This will open the PR creation form, where you can enter a title and description for the PR, and choose which branch to merge the changes into. Click "Create" to create the PR. +To create a PR, make sure you are on a separate branch from the main branch, and push your code changes to the remote repository. In the **Source Control** tab, select the **Create Pull Request** button. This will open the PR creation form, where you can enter a title and description for the PR, and choose which branch to merge the changes into. select **Create** to create the PR. -To review a PR, click the "Review Pull Request" button in the "Source Control" tab, and select the PR you want to review. This will open the PR in a new editor window, where you can review the code changes and leave comments. Once you are satisfied with the code changes, you can click the "Merge" button to merge the PR into the main branch. +To review a PR, select the **Review Pull Request** button in the **Source Control** tab, and select the PR you want to review. This will open the PR in a new editor window, where you can review the code changes and leave comments. Once you are satisfied with the code changes, you can select the **Merge** button to merge the PR into the main branch. Learn more about Pull Requests in the [VS Code's GitHub documentation](https://code.visualstudio.com/docs/sourcecontrol/github). \ No newline at end of file From 29cff8c85fcdb2d216ba55ceb447a546e4e45f8d Mon Sep 17 00:00:00 2001 From: Harald Kirschner Date: Fri, 17 Feb 2023 11:30:07 -0800 Subject: [PATCH 4/8] First round of images --- .../images/intro/codespace-create.png | 3 ++ .../images/intro/github-clone.png | 3 ++ .../images/intro/remote-repo.png | 3 ++ .../images/intro/scm-init-publish.png | 3 ++ .../images/intro/scm-staging.png | 3 ++ docs/sourcecontrol/images/intro/timeline.png | 3 ++ docs/sourcecontrol/intro-to-git.md | 36 +++++++++---------- 7 files changed, 36 insertions(+), 18 deletions(-) create mode 100644 docs/sourcecontrol/images/intro/codespace-create.png create mode 100644 docs/sourcecontrol/images/intro/github-clone.png create mode 100644 docs/sourcecontrol/images/intro/remote-repo.png create mode 100644 docs/sourcecontrol/images/intro/scm-init-publish.png create mode 100644 docs/sourcecontrol/images/intro/scm-staging.png create mode 100644 docs/sourcecontrol/images/intro/timeline.png diff --git a/docs/sourcecontrol/images/intro/codespace-create.png b/docs/sourcecontrol/images/intro/codespace-create.png new file mode 100644 index 0000000000..bd07496f3a --- /dev/null +++ b/docs/sourcecontrol/images/intro/codespace-create.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9a92d8afa6935e63626d165386e48ccfa3c182fd748e6bc3235475fe476dd6ad +size 245078 diff --git a/docs/sourcecontrol/images/intro/github-clone.png b/docs/sourcecontrol/images/intro/github-clone.png new file mode 100644 index 0000000000..74bfe8a94a --- /dev/null +++ b/docs/sourcecontrol/images/intro/github-clone.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d39d771a742afc6ea8d9e6e6802dd188991a0493a639d79a851c7b82de801fe2 +size 175311 diff --git a/docs/sourcecontrol/images/intro/remote-repo.png b/docs/sourcecontrol/images/intro/remote-repo.png new file mode 100644 index 0000000000..bc6c7d82d6 --- /dev/null +++ b/docs/sourcecontrol/images/intro/remote-repo.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2cf9f02b82d545491482eab57e2d61cf53903615ecfc2bb24dcd63f8305e912f +size 52991 diff --git a/docs/sourcecontrol/images/intro/scm-init-publish.png b/docs/sourcecontrol/images/intro/scm-init-publish.png new file mode 100644 index 0000000000..286b1f7878 --- /dev/null +++ b/docs/sourcecontrol/images/intro/scm-init-publish.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:74a4d0af06cb7e257c6db86b593ec0b851f18c66deea5ad1faf0db23fc5fcaf5 +size 101543 diff --git a/docs/sourcecontrol/images/intro/scm-staging.png b/docs/sourcecontrol/images/intro/scm-staging.png new file mode 100644 index 0000000000..5e04b041e4 --- /dev/null +++ b/docs/sourcecontrol/images/intro/scm-staging.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7b2b1a064dc652cc592341bf22f15479fa4ad4c9935e1c75a8a9eba50928fbdb +size 148605 diff --git a/docs/sourcecontrol/images/intro/timeline.png b/docs/sourcecontrol/images/intro/timeline.png new file mode 100644 index 0000000000..12e8029608 --- /dev/null +++ b/docs/sourcecontrol/images/intro/timeline.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f998a74e69933e64e251c13ac96098269030dac334db192be0abd655792c8698 +size 140909 diff --git a/docs/sourcecontrol/intro-to-git.md b/docs/sourcecontrol/intro-to-git.md index d64dd07c5e..874316a55c 100644 --- a/docs/sourcecontrol/intro-to-git.md +++ b/docs/sourcecontrol/intro-to-git.md @@ -1,21 +1,21 @@ # Intro Git in Visual Studio Code ## Introduction -Git and GitHub are powerful tools for managing code, collaborating with others, and keeping track of changes to your codebase. Whether you're new to coding or a seasoned professional, learning how to set up Git and GitHub in VS Code is a valuable skill to have. - -VS Code's intuitive UI makes it easy for beginners to understand and perform common Git actions, such as pulling from and pushing to a remote repository, creating and merging branches, and staging and committing code changes. For seasoned professional, the ability to perform Git actions directly in the editor saves time and effort compared to using the Terminal. The integrated nature of VS Code's Git features also allows for a seamless workflow, without the need to switch between the editor and the Terminal. +Want to easily manage your code and collaborate with others? Git and GitHub are the tools you need! And with VS Code, you can set up and use them in a snap. Even if you're a beginner, VS Code's user-friendly interface will guide you through common Git actions like pushing and pulling code, creating and merging branches, and committing code changes. And if you're a pro, you'll love the ability to perform Git actions directly within the editor, saving you time and effort compared to using the Terminal. Plus, the seamless workflow between VS Code and Git means you can stay in your editor and get more done. ## Setup Git in VS Code -To use Git and GitHub in VS Code, first make sure you have Git installed on your computer. If Git is missing the *Source Control* tab will show instructions on how to install it. Make sure to restart VS Code afterwards. +To use Git and GitHub in VS Code, first make sure you [have Git installed on your computer](https://git-scm.com/downloads). If Git is missing the *Source Control* tab will show instructions on how to install it. Make sure to restart VS Code afterwards. -(Todo: Clarify authentication setup for GitHub from within VS Code) +Optionally you can sign into VS Code with your GitHub account in the **Accounts** menu to enables additional features like settings sync, but also cloning and publishing repositories from GitHub. ## Open a Git repository -VS Code provides several ways to get started in a Git repository. +VS Code provides several ways to get started in a Git repository, from local to remote cloud-powered environments like GitHub Codespaces. + +### Clone a repository locally -### Clone a repository +![Screenshot of the Clone Repository quick prompt, searching fot repositories with the name vscode](images/intro/github-clone.png) To clone a repository from GitHub, execute the **Git: Clone** command or select the **Clone Repository** button in the **Source Control** view. If you clone from GitHub, VS Code will prompt you to authenticate with GitHub. This will allow you to search all available repositories and clone private repositories. For other Git providers enter the repository URL and select **Clone** and pick a folder. VS Code will open it once the repository has been cloned. @@ -27,15 +27,17 @@ To initialize a new local repository, pick an existing or new folder on your com Once you have a local Git repository set up, you can publish it to GitHub. This will create a new repository on your GitHub account, and push your local code to the remote repository. It is great for backing up your code, collaborating with others, and automating your workflow with GitHub Actions. -Use the **Publish to GitHub** command or the **Publish Repository** button in the **Source Control** tab. This will prompt you to authenticate with GitHub. You can then choose a name and description for the repository, and whether to make it public or private. Once the repository has been created, VS Code will push your local code to the remote repository. +![Source Control view for a workspace without git will offer to Initialize a Git repo or Publish to GitHub](images/intro/scm-init-publish.png) + +Use the **Publish to GitHub** command button in the **Source Control** tab. You can then choose a name and description for the repository, and whether to make it public or private. Once the repository has been created, VS Code will push your local code to the remote repository. Your code is now backed up on GitHub, and you can start collaborating with others with commits and pull requests. ### Open a GitHub repository in a Codespace -Codespaces let you to open a GitHub repository in a full configured cloud-based development environment, allowing you to develop in a browser without having to install any software on your local computer. They include free usage for individuals which makes it easy to getting started in open source. +GitHubCodespaces let you open a GitHub repository in a full configured cloud-based development environment, allowing you to develop in a browser without having to install any software on your local computer. They include free usage for individuals which makes it easy to getting started in open source. Install the [GitHub Codespaces](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) extension into VS Code and sign in with GitHub. Run the **Codespaces: Create New Codespace** command and pick the repository and branch you want to open. The Codespace will open in a new window. -(Todo: Add video loop) +![Creating a Codespace from a repo within desktop VS Code](images/intro/codespace-create.png) Alternatively, you can also start from a template from the [GitHub's Codespaces site](https://github.com/codespaces/templates). If you already have a Codespace open in your browser, you can open it in your Desktop VS Code by running the **Codespaces: Open in VS Code Desktop** command. Learn more about Codespaces to forwarding ports. @@ -45,25 +47,23 @@ VS Code remote repositories allows you to browse and edit a GitHub repository wi First install the the [GitHub Repositories](https://marketplace.visualstudio.com/items?itemName=GitHub.remotehub) extension. Run the command **Remote Repositories: Open Remote Repository...** or use the **Open Remote Repository** button the Explorer view. Search and select the GitHub repository that you want to open. -(Todo: Add screenshot) - -Browse, search, and edit files as you would in a local repository. Commit from the *Source Control* will go directly be integrated to the remote repository. The remote repository can not execute any code or run terminal commands. +![Remote Repositories opening a remote GitHub repo, pull request or Azure repo](images/intro/remote-repo.png) -(Todo: Link to further docs on remote repositories) +> **Tip:** If you need to execute code or run terminal commands, you can seamlessly switch from a remote repository to a Codespace with the command **Continue Working on**. ## Staging and committing code changes Once you have a Git repository set up, you can start tracking code changes by staging and committing your newly created and edited code. -Tip: Commit early and often. This will make it easier to revert to previous versions of your code if needed. +![Source Control view with one file staged and other changes, a diff showing in the editor that highlights the changes](images/intro/scm-staging.png) -(Todo: Add screenshot for staging and committing) +> **Tip:** Commit early and often. This will make it easier to revert to previous versions of your code if needed. To stage a file, select the **+** (plus) icon next to the file in the **Source Control** tab. This will add the file to the **Staged Changes** section, indicating that it will be included in the next commit. Staged changes can also be discarded by selecting the **−** (minus) icon next to the file. -To commit your staged changes, type a commit message and select the **Commit** button. This will save your changes to the local Git repository, allowing you to revert to previous versions of your code if needed. All file changes and commits are shown in the **Timeline** section. +To commit your staged changes, type a commit message and select the **Commit** button. This will save your changes to the local Git repository, allowing you to revert to previous versions of your code if needed. All local file changes and commits can be navigated in the **Timeline** section. -(Todo: Add screenshot for timeline) +![Timeline view with one item selected and its change being shown in the editor](images/intro/timeline.png) ## Pushing and pulling remote changes From 99040730c88c91244b672027e90a1b8a993aa9eb Mon Sep 17 00:00:00 2001 From: Harald Kirschner Date: Fri, 17 Feb 2023 11:41:37 -0800 Subject: [PATCH 5/8] Last images --- docs/sourcecontrol/images/intro/branch-indicator.png | 3 +++ docs/sourcecontrol/images/intro/sync.png | 3 +++ docs/sourcecontrol/intro-to-git.md | 10 +++++----- 3 files changed, 11 insertions(+), 5 deletions(-) create mode 100644 docs/sourcecontrol/images/intro/branch-indicator.png create mode 100644 docs/sourcecontrol/images/intro/sync.png diff --git a/docs/sourcecontrol/images/intro/branch-indicator.png b/docs/sourcecontrol/images/intro/branch-indicator.png new file mode 100644 index 0000000000..599fdccbde --- /dev/null +++ b/docs/sourcecontrol/images/intro/branch-indicator.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:48af35da3f378b765cb051a472b44dd598b837bc00a2379511dfcadc88dfe9ea +size 21761 diff --git a/docs/sourcecontrol/images/intro/sync.png b/docs/sourcecontrol/images/intro/sync.png new file mode 100644 index 0000000000..9290b4af3d --- /dev/null +++ b/docs/sourcecontrol/images/intro/sync.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a81d9629cc23483275993d796d1c97bc9f479497b57f5ec2583d582c8797cab2 +size 43064 diff --git a/docs/sourcecontrol/intro-to-git.md b/docs/sourcecontrol/intro-to-git.md index 874316a55c..4ae2156cba 100644 --- a/docs/sourcecontrol/intro-to-git.md +++ b/docs/sourcecontrol/intro-to-git.md @@ -69,7 +69,7 @@ To commit your staged changes, type a commit message and select the **Commit** b Once you have made commits to your local Git repository, you can push them to the remote repository. The **Sync** button will indicate how many commits are going to be pushed and pulled. selecting **Sync** button will download (pull) any new remote commits and upload (push) new local commits to the remote repository. -(todo: Add screenshot for sync) +![Sync button with one change to push](images/intro/sync.png) > Tip: Make sure to enable **Git: Autofetch** to always get an up-to-date remote commit indicators. @@ -77,19 +77,19 @@ Once you have made commits to your local Git repository, you can push them to th ## Using branches -In Git, branches allow you to work on multiple versions of your codebase simultaneously. This is useful for experimenting with new features or making large code changes without affecting the main codebase. +In Git, [branches](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches) allow you to work on multiple versions of your codebase simultaneously. This is useful for experimenting with new features or making large code changes without affecting the main codebase. -(todo: Add screenshot for branch indicator) +![Branch indicator in the status bar](images/intro/branch-indicator.png) The branch dropdown in the status bar shows the current branch and lets you switch to new and existing branches. To create a new branch, select the branch indicator and choose to create it from the current branch or another local one. Type a name for the new branch, and confirm. This will create a new branch and switch you to it, allowing you to make changes to your code without affecting the main branch. -> Tip: If you use the GitHub Pull Request extension you can create a branch directly from an issue, which get you started coding in a new new local branch and automatically prefill the pull request for you. +> **Tip:** If you use the GitHub Pull Request extension you can create a branch directly from an issue, which get you started coding in a new new local branch and automatically prefill the pull request for you. To push the branch to the remote repository, select **Publish** in the **Source Control** tab. This will create a new branch on the remote repository, allowing you to collaborate with others on the branch. ### Creating and reviewing GitHub Pull Requests -In Git and GitHub, Pull Requests (PRs) are a way for collaborators to review and merge code changes from separate branches into the main branch. This allows teams to review and approve code changes before they are incorporated into the main codebase, ensuring that only high-quality code is merged. +In Git and GitHub, [Pull Requests (PRs)](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests) are a way for collaborators to review and merge code changes from separate branches into the main branch. This allows teams to review and approve code changes before they are incorporated into the main codebase, ensuring that only high-quality code is merged. To use Pull Requests in VS Code, you will need to install the [GitHub Pull Request & Issues](https://marketplace.visualstudio.com/items?itemName=GitHub.vscode-pull-request-github) extension. This extension adds PR and issue tracking functionality to VS Code, allowing you to create, review, and merge PRs from within the editor. From 2d25bdcbaf3bdd9e6269302025cc85d7a6eb6d1f Mon Sep 17 00:00:00 2001 From: Harald Kirschner Date: Tue, 21 Feb 2023 11:12:07 -0800 Subject: [PATCH 6/8] Adding git bash --- docs/sourcecontrol/images/intro/git-bash.png | 3 ++ docs/sourcecontrol/intro-to-git.md | 29 +++++++++++++++++--- 2 files changed, 28 insertions(+), 4 deletions(-) create mode 100644 docs/sourcecontrol/images/intro/git-bash.png diff --git a/docs/sourcecontrol/images/intro/git-bash.png b/docs/sourcecontrol/images/intro/git-bash.png new file mode 100644 index 0000000000..42b2054f87 --- /dev/null +++ b/docs/sourcecontrol/images/intro/git-bash.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed5bc0ca78ebc3535de95680efc0a7773d7d52149f62d22190eb5b0a067ecb81 +size 59910 diff --git a/docs/sourcecontrol/intro-to-git.md b/docs/sourcecontrol/intro-to-git.md index 4ae2156cba..20e14bf526 100644 --- a/docs/sourcecontrol/intro-to-git.md +++ b/docs/sourcecontrol/intro-to-git.md @@ -1,6 +1,13 @@ -# Intro Git in Visual Studio Code +--- +Order: 2 +Area: sourcecontrol +TOCTitle: Intro to Git +PageTitle: Intro to Git +DateApproved: 2/21/2023 +MetaDescription: Get started with Git and take control of your code! Our beginner's guide covers everything you need to know, from setting up a repository to committing changes and collaborating with others. Learn Git today and streamline your development workflow. +--- +# Intro to Git in Visual Studio Code -## Introduction Want to easily manage your code and collaborate with others? Git and GitHub are the tools you need! And with VS Code, you can set up and use them in a snap. Even if you're a beginner, VS Code's user-friendly interface will guide you through common Git actions like pushing and pulling code, creating and merging branches, and committing code changes. And if you're a pro, you'll love the ability to perform Git actions directly within the editor, saving you time and effort compared to using the Terminal. Plus, the seamless workflow between VS Code and Git means you can stay in your editor and get more done. ## Setup Git in VS Code @@ -71,7 +78,7 @@ Once you have made commits to your local Git repository, you can push them to th ![Sync button with one change to push](images/intro/sync.png) -> Tip: Make sure to enable **Git: Autofetch** to always get an up-to-date remote commit indicators. +> **Tip:** Make sure to enable **Git: Autofetch** to always get an up-to-date remote commit indicators. Push and pull can also be performed individually by using their respective commands. @@ -97,4 +104,18 @@ To create a PR, make sure you are on a separate branch from the main branch, and To review a PR, select the **Review Pull Request** button in the **Source Control** tab, and select the PR you want to review. This will open the PR in a new editor window, where you can review the code changes and leave comments. Once you are satisfied with the code changes, you can select the **Merge** button to merge the PR into the main branch. -Learn more about Pull Requests in the [VS Code's GitHub documentation](https://code.visualstudio.com/docs/sourcecontrol/github). \ No newline at end of file +Learn more about Pull Requests in the [VS Code's GitHub documentation](https://code.visualstudio.com/docs/sourcecontrol/github). + +## Using Git in the built-in terminal + +As Git state is kept in the local repository you can easily switch between VS Code's UI, the [built-in terminal](/docs/editor/integrated-terminal), or external tools like [GitHub Desktop](https://desktop.github.com/). Related, you can also set up [VS Code as your default Git editor](/docs/sourcecontrol/overview#_vs-code-as-git-editor), allowing you to use VS Code to edit commit messages and other Git-related files. + +### Git Bash on Windows + +Git Bash is a popular shell environment for Windows that provides a Unix-like command-line interface for working with Git and other command-line tools. Visual Studio Code's integrated terminal supports Git Bash as a shell, allowing you to seamlessly integrate Git Bash into your development workflow. Installing Git on your Windows machine will also install Git Bash if it wasn't deselected during the installation steps. + +![Selecting Git Bash as shell in Visual Studio Code's built-in terminal](images/intro/git-bash.png) + + Start by opening **View** > **Terminal** (`kb(workbench.action.terminal.toggleTerminal)`). Click on the dropdown arrow next to the `+` icon in the terminal panel to pick a new shell to open. If Git Bash is installed, it will be shown in the list. You can toggle between different terminals and shells in the Terminal sidebar. With Git Bash configured in Visual Studio Code, you can now use all of your favorite Git commands directly from the terminal in your code editor. + + If you want to set Git Bash as your default shell, open the Terminal dropdown (next to the `+` icon) and select **Select Default Shell**. This will open a list of available shells, including Git Bash. Selecting Git Bash will set it as your default shell, and all future terminals will be opened with Git Bash. More advanced tips can be found in the [terminal documentation](/docs/editor/integrated-terminal). \ No newline at end of file From dab0fb12afc273d849cd13c083a384f9c51e5dd1 Mon Sep 17 00:00:00 2001 From: Harald Kirschner Date: Tue, 21 Feb 2023 11:15:04 -0800 Subject: [PATCH 7/8] Compressing images --- docs/sourcecontrol/images/intro/branch-indicator.png | 4 ++-- docs/sourcecontrol/images/intro/codespace-create.png | 4 ++-- docs/sourcecontrol/images/intro/git-bash.png | 4 ++-- docs/sourcecontrol/images/intro/github-clone.png | 4 ++-- docs/sourcecontrol/images/intro/remote-repo.png | 4 ++-- docs/sourcecontrol/images/intro/scm-init-publish.png | 4 ++-- docs/sourcecontrol/images/intro/scm-staging.png | 4 ++-- docs/sourcecontrol/images/intro/sync.png | 4 ++-- docs/sourcecontrol/images/intro/timeline.png | 4 ++-- 9 files changed, 18 insertions(+), 18 deletions(-) diff --git a/docs/sourcecontrol/images/intro/branch-indicator.png b/docs/sourcecontrol/images/intro/branch-indicator.png index 599fdccbde..9578535802 100644 --- a/docs/sourcecontrol/images/intro/branch-indicator.png +++ b/docs/sourcecontrol/images/intro/branch-indicator.png @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:48af35da3f378b765cb051a472b44dd598b837bc00a2379511dfcadc88dfe9ea -size 21761 +oid sha256:3d7cfeee7455a70a3e4b3743e206e0fc6c646ec95d7041e3b83f7b4938be3f86 +size 4225 diff --git a/docs/sourcecontrol/images/intro/codespace-create.png b/docs/sourcecontrol/images/intro/codespace-create.png index bd07496f3a..98ee6a2413 100644 --- a/docs/sourcecontrol/images/intro/codespace-create.png +++ b/docs/sourcecontrol/images/intro/codespace-create.png @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:9a92d8afa6935e63626d165386e48ccfa3c182fd748e6bc3235475fe476dd6ad -size 245078 +oid sha256:b40045a2b318858dc266fc3b1f7920385c5a1d45af84f4ab80e9e482d19e1362 +size 57540 diff --git a/docs/sourcecontrol/images/intro/git-bash.png b/docs/sourcecontrol/images/intro/git-bash.png index 42b2054f87..a077ba8fc3 100644 --- a/docs/sourcecontrol/images/intro/git-bash.png +++ b/docs/sourcecontrol/images/intro/git-bash.png @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:ed5bc0ca78ebc3535de95680efc0a7773d7d52149f62d22190eb5b0a067ecb81 -size 59910 +oid sha256:292b1963448d3351d7cf532c93b893dde7820a58a6f1be499d775a64cec5a924 +size 19167 diff --git a/docs/sourcecontrol/images/intro/github-clone.png b/docs/sourcecontrol/images/intro/github-clone.png index 74bfe8a94a..0c4e9de8cc 100644 --- a/docs/sourcecontrol/images/intro/github-clone.png +++ b/docs/sourcecontrol/images/intro/github-clone.png @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:d39d771a742afc6ea8d9e6e6802dd188991a0493a639d79a851c7b82de801fe2 -size 175311 +oid sha256:b3f0f6769f4f25ccf13510761b1e0cc5e2b26901eae8fbeacfcc4ba9bf102741 +size 38239 diff --git a/docs/sourcecontrol/images/intro/remote-repo.png b/docs/sourcecontrol/images/intro/remote-repo.png index bc6c7d82d6..190247d41c 100644 --- a/docs/sourcecontrol/images/intro/remote-repo.png +++ b/docs/sourcecontrol/images/intro/remote-repo.png @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:2cf9f02b82d545491482eab57e2d61cf53903615ecfc2bb24dcd63f8305e912f -size 52991 +oid sha256:2478bba4d4a12fe21cc9c1caadd1284df5da6fc793e48e116cfa606c1013cf8d +size 11574 diff --git a/docs/sourcecontrol/images/intro/scm-init-publish.png b/docs/sourcecontrol/images/intro/scm-init-publish.png index 286b1f7878..9485c10b0f 100644 --- a/docs/sourcecontrol/images/intro/scm-init-publish.png +++ b/docs/sourcecontrol/images/intro/scm-init-publish.png @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:74a4d0af06cb7e257c6db86b593ec0b851f18c66deea5ad1faf0db23fc5fcaf5 -size 101543 +oid sha256:0cdf318eda2b192868f86aa9df6489036a1d380516a3eb6ae19a743d5a6821cf +size 20738 diff --git a/docs/sourcecontrol/images/intro/scm-staging.png b/docs/sourcecontrol/images/intro/scm-staging.png index 5e04b041e4..7f0a6cc159 100644 --- a/docs/sourcecontrol/images/intro/scm-staging.png +++ b/docs/sourcecontrol/images/intro/scm-staging.png @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:7b2b1a064dc652cc592341bf22f15479fa4ad4c9935e1c75a8a9eba50928fbdb -size 148605 +oid sha256:1bcf334e51970a9dc45b15c36645c93d02225bc7b6dee5918f2117b960942a04 +size 54499 diff --git a/docs/sourcecontrol/images/intro/sync.png b/docs/sourcecontrol/images/intro/sync.png index 9290b4af3d..801c6d6a6e 100644 --- a/docs/sourcecontrol/images/intro/sync.png +++ b/docs/sourcecontrol/images/intro/sync.png @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:a81d9629cc23483275993d796d1c97bc9f479497b57f5ec2583d582c8797cab2 -size 43064 +oid sha256:10557c1f4a7d55282de905c13c9837663c90bb56eb482b60d8520351b70c8988 +size 11968 diff --git a/docs/sourcecontrol/images/intro/timeline.png b/docs/sourcecontrol/images/intro/timeline.png index 12e8029608..cfaf145afe 100644 --- a/docs/sourcecontrol/images/intro/timeline.png +++ b/docs/sourcecontrol/images/intro/timeline.png @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:f998a74e69933e64e251c13ac96098269030dac334db192be0abd655792c8698 -size 140909 +oid sha256:bb6eb9b6bb532fd85f0962d8a4c37f1163adff8a5092d3a3edf3a2995e165fae +size 56422 From c0cc11d65e12bfd08f8d330217f6e3e3cc194aac Mon Sep 17 00:00:00 2001 From: Harald Kirschner Date: Tue, 21 Feb 2023 17:54:42 -0800 Subject: [PATCH 8/8] re-export from figma, 1x resolution --- docs/sourcecontrol/images/intro/branch-indicator.png | 4 ++-- docs/sourcecontrol/images/intro/codespace-create.png | 4 ++-- docs/sourcecontrol/images/intro/git-bash.png | 4 ++-- docs/sourcecontrol/images/intro/github-clone.png | 4 ++-- docs/sourcecontrol/images/intro/scm-init-publish.png | 4 ++-- docs/sourcecontrol/images/intro/scm-staging.png | 4 ++-- docs/sourcecontrol/images/intro/sync.png | 4 ++-- docs/sourcecontrol/images/intro/timeline.png | 4 ++-- 8 files changed, 16 insertions(+), 16 deletions(-) diff --git a/docs/sourcecontrol/images/intro/branch-indicator.png b/docs/sourcecontrol/images/intro/branch-indicator.png index 9578535802..897c9f5567 100644 --- a/docs/sourcecontrol/images/intro/branch-indicator.png +++ b/docs/sourcecontrol/images/intro/branch-indicator.png @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:3d7cfeee7455a70a3e4b3743e206e0fc6c646ec95d7041e3b83f7b4938be3f86 -size 4225 +oid sha256:fd8b9b0669ccece1605e93edb4f300e09cd775354899f80b0fd4a4a2c677f8e5 +size 2134 diff --git a/docs/sourcecontrol/images/intro/codespace-create.png b/docs/sourcecontrol/images/intro/codespace-create.png index 98ee6a2413..4877960145 100644 --- a/docs/sourcecontrol/images/intro/codespace-create.png +++ b/docs/sourcecontrol/images/intro/codespace-create.png @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:b40045a2b318858dc266fc3b1f7920385c5a1d45af84f4ab80e9e482d19e1362 -size 57540 +oid sha256:eac536bb31ce25c5f1b09548e4d8ba3c035e72da8bcabc3aeeb37f81f2dada88 +size 24024 diff --git a/docs/sourcecontrol/images/intro/git-bash.png b/docs/sourcecontrol/images/intro/git-bash.png index a077ba8fc3..4bbda69d78 100644 --- a/docs/sourcecontrol/images/intro/git-bash.png +++ b/docs/sourcecontrol/images/intro/git-bash.png @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:292b1963448d3351d7cf532c93b893dde7820a58a6f1be499d775a64cec5a924 -size 19167 +oid sha256:78f8e62a2231d14c2ae2a30fed1c81864cd88e35b28d0da88d12f1b5ed259401 +size 9078 diff --git a/docs/sourcecontrol/images/intro/github-clone.png b/docs/sourcecontrol/images/intro/github-clone.png index 0c4e9de8cc..220b8e2195 100644 --- a/docs/sourcecontrol/images/intro/github-clone.png +++ b/docs/sourcecontrol/images/intro/github-clone.png @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:b3f0f6769f4f25ccf13510761b1e0cc5e2b26901eae8fbeacfcc4ba9bf102741 -size 38239 +oid sha256:aafd21bf4deb28efdd65949aa45d579af3d569031eed908ce62ae56205f9898d +size 18442 diff --git a/docs/sourcecontrol/images/intro/scm-init-publish.png b/docs/sourcecontrol/images/intro/scm-init-publish.png index 9485c10b0f..b4a2fd41c9 100644 --- a/docs/sourcecontrol/images/intro/scm-init-publish.png +++ b/docs/sourcecontrol/images/intro/scm-init-publish.png @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:0cdf318eda2b192868f86aa9df6489036a1d380516a3eb6ae19a743d5a6821cf -size 20738 +oid sha256:02988bcbf8dee5ca32941e44ec90ce48e318a260936e9e7494a535c48d71b160 +size 9968 diff --git a/docs/sourcecontrol/images/intro/scm-staging.png b/docs/sourcecontrol/images/intro/scm-staging.png index 7f0a6cc159..85862b9822 100644 --- a/docs/sourcecontrol/images/intro/scm-staging.png +++ b/docs/sourcecontrol/images/intro/scm-staging.png @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:1bcf334e51970a9dc45b15c36645c93d02225bc7b6dee5918f2117b960942a04 -size 54499 +oid sha256:12ac6454d88d19fc7ecb6dd981ba00bcebed9f920f3ccaf4fcaea09cba2daa17 +size 21981 diff --git a/docs/sourcecontrol/images/intro/sync.png b/docs/sourcecontrol/images/intro/sync.png index 801c6d6a6e..3359e365a1 100644 --- a/docs/sourcecontrol/images/intro/sync.png +++ b/docs/sourcecontrol/images/intro/sync.png @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:10557c1f4a7d55282de905c13c9837663c90bb56eb482b60d8520351b70c8988 -size 11968 +oid sha256:34264a6710c1eecd9e7fd52777255933d27ba67a6b08dc35dfbb76ffaca3b25e +size 3294 diff --git a/docs/sourcecontrol/images/intro/timeline.png b/docs/sourcecontrol/images/intro/timeline.png index cfaf145afe..6d675eb930 100644 --- a/docs/sourcecontrol/images/intro/timeline.png +++ b/docs/sourcecontrol/images/intro/timeline.png @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:bb6eb9b6bb532fd85f0962d8a4c37f1163adff8a5092d3a3edf3a2995e165fae -size 56422 +oid sha256:fbf3c57a962ad3b03fd4e75d71b17980e5fb3a20d80487013f6801954d3a800e +size 23560