├── .gitignore ├── 1-welcome ├── README.md ├── how-to-install-vs.md └── images │ ├── github-git-vs-workingtogether.png │ └── local-and-remote-repositories.png ├── 2-github ├── README.md └── images │ ├── Title Card - Accessing Code in the Cloud with GitHub.png │ ├── clone-a-repository.png │ ├── clone-from-github.png │ └── get-started-clone-a-repository.png ├── 3-revision-history ├── README.md └── images │ ├── Title Card - Viewing Your Revision History in Visual Studio.png │ ├── answer3.png │ └── git-repository-window.png ├── 4-sync-to-cloud ├── README.md └── images │ ├── Title Card - Syncing your Code to the Cloud.png │ ├── create-a-git-repository-window-signed-in.png │ ├── create-a-git-repository-window.png │ ├── create-git-repository.png │ ├── open-in-browser.png │ └── sign-in-to-github.png ├── 5-daily-workflow ├── README.md └── images │ ├── Title Card - Daily Workflow with GitHub in Visual Studio.png │ ├── git-changes-commit-message.png │ ├── git-changes-committed.png │ ├── git-changes-modified.png │ ├── git-changes-staged.png │ └── git-states.png ├── CODE_OF_CONDUCT.md ├── LICENSE ├── README.md ├── SECURITY.md └── SUPPORT.md /.gitignore: -------------------------------------------------------------------------------- 1 | ################################################################################ 2 | # This .gitignore file was automatically created by Microsoft(R) Visual Studio. 3 | ################################################################################ 4 | 5 | /.vs/Git-Learning-Series/FileContentIndex 6 | /.vs/Git-Learning-Series/v17 7 | /.vs 8 | -------------------------------------------------------------------------------- /1-welcome/README.md: -------------------------------------------------------------------------------- 1 | # Welcome to the Intro to GitHub in Visual Studio Series 2 | This is the first lesson in the Introduction to Version Control with GitHub email series! We’re excited to get you started backing up your code to the cloud, syncing across devices, and viewing the revision history of your codebase using GitHub integrated with Visual Studio. In this first email, we’ll give you the email schedule rundown, give you a brief introduction to Git and Version Control, and show you all the tools you’ll need for this series. 3 | 4 | ## Prerequisite tools 5 | * [Visual Studio](https://aka.ms/vsgitlearn-1-vsdownload) or [Visual Studio for Mac](https://aka.ms/vsgitlearn-1-vsmacdownload) – check out our [more detailed instructions](how-to-install-vs.md) for extra help 6 | * [GitHub account](https://aka.ms/vsgitlearn-1-create-gh-account) 7 | 8 | ## What to expect 9 | During the series you will learn the basics of using Git with Visual Studio. Here is a rundown of what the next few weeks will look like. 10 | * Lesson 1 – This welcome email! 11 | * Lesson 2 – Cloning a repository from GitHub 12 | * Lesson 3 – Exploring a Git repository using Visual Studio 13 | * Lesson 4 – Adding your existing code to Git and GitHub 14 | * Lesson 5 – Daily Workflow with GitHub in Visual Studio and Next Steps 15 | To start your journey let’s look at a brief overview of what Git and Version Control are, and how to get started with a GitHub account. 16 | 17 | ## What is Git and Version Control? 18 | Version control makes it possible to track changes you make to your code over time so you can both track your progress and revert to specific versions. Visual Studio makes it easy to work with Git, which is the most widely used modern version control system. Git is a distributed source control system meaning that to work on your code, your computer needs to have a full copy (clone) of your code’s repository. This gives you the ability to make changes in situations when you don’t have internet access. You will also have multiple backups of your code, a local Git repository on every computer you work on. 19 | 20 | ![GitHub, Git, and Visual Studio working together](images/github-git-vs-workingtogether.png) 21 | 22 | ## What is a repository? 23 | It is the database that Git uses to track changes made to your code over time. You can update this Git database, your Git repository, by (committing) your changes which would store a picture of your code changes to your local Git repository. Then when you are ready, you can (push) your local Git changes to your remote repository so that you and/or others can access these changes from other locations. 24 | 25 | ![Local and Remote Repositories](images/local-and-remote-repositories.png) 26 | 27 | ## How’d it Go? 28 | Congratulations! You're all set up to be successful learning with this series. 29 | Please take this quick [survey](https://aka.ms/vsgitlearn-1-survey) to give use your thoughts on this lesson! 30 | 31 | -------------------------------------------------------------------------------- /1-welcome/how-to-install-vs.md: -------------------------------------------------------------------------------- 1 | # Install Visual Studio 2 | 3 | ## If you're on Windows 4 | 1. Go to the [Develop .NET applications page](https://visualstudio.microsoft.com/vs/features/net-development/) of the Visual Studio website 5 | 1. Find the "Download Visual Studio with .NET" dropdown and select "Community 2022" 6 | 1. Run the exe and let Visual Studio download 7 | 1. Wait for everything to install 8 | 1. Sign in to Visual Studio 9 | 1. Done ?? 10 | 11 | ## If you're on Mac 12 | 1. Go to the [Build Web Apps using .NET Core page](https://visualstudio.microsoft.com/vs/mac/net/) of the Visual Studio website 13 | 1. Select the VisualStudioforMacInstaller.dmg to mount the installer, then run it by double-clicking the arrow logo 14 | 2. Select **Open** 15 | 1. An alert will appear asking you to acknowledge the privacy and license terms. Follow the links to read them, then press **Continue** if you agree 16 | 1. The list of available workloads is displayed. Select the .NET Core component. 17 | 1. Press **Install** 18 | 1. Sign in and choose your keyboard preferences 19 | 1. Done ?? 20 | 21 | ## Want more help? 22 | If you want more detailed installation instructions, check out the Microsoft Documentation. 23 | * If you're on Windows, go to [Install Visual Studio](https://docs.microsoft.com/visualstudio/install/install-visual-studio?view=vs-2022) 24 | * If you're on Mac, go to [Install Visual Studio for Mac](https://docs.microsoft.com/visualstudio/mac/installation?view=vsmac-2019) 25 | 26 | Check out the [Learn to code in Visual Studio](https://visualstudio.microsoft.com/vs/getting-started/) page to learn more about the installation process, how to get started with Visual Studio, and how to make it your own with themes! ?? 27 | -------------------------------------------------------------------------------- /1-welcome/images/github-git-vs-workingtogether.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/Git-Learning-Series/869f5829fe4cb3bcb3275fc7387d04b0dccf478a/1-welcome/images/github-git-vs-workingtogether.png -------------------------------------------------------------------------------- /1-welcome/images/local-and-remote-repositories.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/Git-Learning-Series/869f5829fe4cb3bcb3275fc7387d04b0dccf478a/1-welcome/images/local-and-remote-repositories.png -------------------------------------------------------------------------------- /2-github/README.md: -------------------------------------------------------------------------------- 1 | # Accessing Code in the Cloud with GitHub 2 | In this lesson, we’ll go over the basics of Git and GitHub by experimenting with the remote repository that this guide is hosted on. Remember, the remote repository is a copy of the code that lives in the cloud, so we need to make a clone on each device we are using for development. This allows for synchronization of your code across all your machines, and the functionality is seamlessly built into Visual Studio. 3 | 4 | ## Cloning a Repo 5 | Let’s start by opening a new tab in your web browser and navigating to the main page of this repository. Now click the green Code drop down button on the Code tab and copy the repository URL. 6 | ![Clone from GitHub](images/clone-from-github.png) 7 | 8 | Open Visual Studio and select the Clone a repository option under the Get started section. Paste the repository URL to the Repository location text box and click the clone button. 9 | 10 |
11 | Get Started - Clone a repository 12 | Clone a repository 13 |
14 | 15 | ## 🚨 Challenge 1 16 | 17 | Time for your first challenge! 18 | 19 | | Challenge | Duration | What you will learn | More information | 20 | | ------------------------------- | ----------- | -------------------------------------- | - | 21 | | Clone this repo to your local machine with Visual Studio | 3 min | How to clone a repo in Visual Studio | [Clone a repo in Visual Studio](https://aka.ms/vsgitlearn-1-clone-repo) | 22 | 23 | ## Video Walkthrough 24 | [drawing](https://youtu.be/iYTm73scl80 "Accessing Code in the Cloud with GitHub") 25 | > 🎥 Click the image above for a video walkthrough of this lesson! 26 | 27 | ## How’d it Go? 28 | Congratulations! You have successfully cloned this open-source project. 29 | Please take this quick [survey](https://aka.ms/vsgitlearn-1-survey) to give use your thoughts on this lesson & challenge! 30 | 31 | ## What's Next? 32 | Check out more open-source projects on GitHub: 33 | * [Trending C# repositories on GitHub today](https://github.com/trending/c%23) 34 | * [halls7588/Data_Structures_in_15_Languages](https://github.com/halls7588/Data_Structures_in_15_Languages) 35 | * [beginner-friendly · GitHub Topics](https://github.com/topics/beginner-friendly?l=c%23) 36 | * [beginner-project · GitHub Topics](https://github.com/topics/beginner-project?l=c%23) 37 | -------------------------------------------------------------------------------- /2-github/images/Title Card - Accessing Code in the Cloud with GitHub.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/Git-Learning-Series/869f5829fe4cb3bcb3275fc7387d04b0dccf478a/2-github/images/Title Card - Accessing Code in the Cloud with GitHub.png -------------------------------------------------------------------------------- /2-github/images/clone-a-repository.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/Git-Learning-Series/869f5829fe4cb3bcb3275fc7387d04b0dccf478a/2-github/images/clone-a-repository.png -------------------------------------------------------------------------------- /2-github/images/clone-from-github.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/Git-Learning-Series/869f5829fe4cb3bcb3275fc7387d04b0dccf478a/2-github/images/clone-from-github.png -------------------------------------------------------------------------------- /2-github/images/get-started-clone-a-repository.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/Git-Learning-Series/869f5829fe4cb3bcb3275fc7387d04b0dccf478a/2-github/images/get-started-clone-a-repository.png -------------------------------------------------------------------------------- /3-revision-history/README.md: -------------------------------------------------------------------------------- 1 | # Viewing Your Revision History in Visual Studio 2 | In this lesson, we will learn how to look at all the different versions, or snapshots of the project over time in Visual Studio. These snapshots are called commits. 3 | 4 | ## Using the Git Repository Window 5 | As mentioned previously, cloning a Git repository creates a local repository copy on your machine. Let’s start by using Visual Studio to explore the local repository we created last time when cloning this project. To do that go to “View > Git Repository” which opens the Git Repository window. It should look like the following: 6 | ![Annotated Git Repository Window](images/git-repository-window.png) 7 | 8 | The Git repository window contains 3 main sections: 9 | 10 | 1- Branches: Git empowers users to multi-task and experiment with their code through branches. If you are working on multiple features at the same time or if you would like to explore ideas without effecting your working code, branching can be very helpful. We haven’t created any branches in this repository so the only local branch that shows is “main” which is created automatically by Git when you first clone. If you expand the remotes/origin folder, you will see a list of the remote branches. 11 | 12 | 2- Git Graph: The Git graph section visualizes the state of your branch. It has three different sections: incoming, outgoing and local history. The incoming section shows incoming commits that your team has been contributing, the outgoing section shows your local commits that you still haven’t pushed, and the local history shows the rest of commits tracked by your local repository. 13 | 14 | 3- Commit Details: clicking any commit on the Git Graph section opens the commit details UI showing the details of commits. You can check the changes introduced by commits by clicking on them which would show a difference. For example, on the previous screenshot you can see that we are viewing one of the changes that has been introduced to the AboutViewModel.cs file. 15 | 16 | ## 🚨 Challenge - Navigate the repository to find a specific commit 17 | 18 | | Challenge | Solution | Duration | What you will learn | 19 | | ------------------------------- | ------------------------------- | ----------- | ----------- | 20 | | Find the hidden message in Commit ID 93e6b07b952a44f5461a20882fa625003e6b0ba0 | [Verify](images/answer3.png) | 3 min | How to filter in the Git Repository window | 21 | 22 | ## Video Walkthrough 23 | [drawing](https://youtu.be/8WxylrNswI8 "Viewing Your Revision History in Visual Studio") 24 | > 🎥 Click the image above for a video walkthrough of this lesson! 25 | 26 | 27 | ## How’d it Go? 28 | Congratulations! You have successfully navigated the repository. 29 | Please take this quick [survey](https://aka.ms/vsgitlearn-1-survey) to give use your thoughts on this lesson & challenge! 30 | 31 | ## What’s next? 32 | Now that you know how to navigate the repository, you can revert to previous commits and learn advanced Git topics like cherry-picking! Check the links below to learn more: 33 | * [Revert changes | Microsoft Learn](https://aka.ms/vsgitlearn-1-revert-changes) 34 | * [Copy commits (cherry-pick) | Microsoft Learn](https://aka.ms/vsgitlearn-1-cherry-pick) 35 | -------------------------------------------------------------------------------- /3-revision-history/images/Title Card - Viewing Your Revision History in Visual Studio.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/Git-Learning-Series/869f5829fe4cb3bcb3275fc7387d04b0dccf478a/3-revision-history/images/Title Card - Viewing Your Revision History in Visual Studio.png -------------------------------------------------------------------------------- /3-revision-history/images/answer3.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/Git-Learning-Series/869f5829fe4cb3bcb3275fc7387d04b0dccf478a/3-revision-history/images/answer3.png -------------------------------------------------------------------------------- /3-revision-history/images/git-repository-window.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/Git-Learning-Series/869f5829fe4cb3bcb3275fc7387d04b0dccf478a/3-revision-history/images/git-repository-window.png -------------------------------------------------------------------------------- /4-sync-to-cloud/README.md: -------------------------------------------------------------------------------- 1 | # Syncing your Code to the Cloud 2 | 3 | In this lesson, we will learn how to add your existing code to the cloud by creating a Git Repository connected to GitHub. 4 | 5 | ## Using the Git Changes Window to Create a New Repo 6 | Get started by opening the Create Git Repository experience which can be accessed through the Git Changes window “Git Changes > Create Git Repository”. Note that the Git Changes window is aware that you are not on a Git repository. Therefore, it is trying to help by providing different options for you to consider including a link to documentation. 7 | 8 | Create Git Repository 9 | 10 | Since you already have a GitHub account, all you need to do is sign in. If you didn’t create a GitHub account in the first lesson, you can create a new account by clicking on the create an account option. 11 | 12 |
13 | Create a Git repository window 14 | Sign in to GitHub 15 |
16 | 17 | Once you sign in, Visual Studio prepopulates your information. You can choose to provide an optional description for your new repository and then click Create and Push. Visual Studio is going to initialize a local Git repository, create a new GitHub repository, and then push your code to it. Note that your repository on GitHub is going to be private by default. Meaning that you are the only one who has access to it. Feel free to uncheck the Private repository checkbox if you would like to create an open-source repository. 18 | 19 | Create a Git repository Window - Signed in 20 | 21 | Once Visual Studio confirms that your new GitHub repository is created, you can check it out on GitHub through the following open in browser functionality in the Git Changes window. 22 | 23 | Open in Browser 24 | 25 | ## 🚨 Challenge - Add your own project to GitHub 26 | 27 | | Challenge | Solution | Duration | What you will learn | More information | 28 | | ------------------------------- | ------------------------------- | ----------- | -------------------------------------- | -------------------------------------- | 29 | | Add your own project code to GitHub | Verify in the browser | 3 min | How to create a new Git Repository on GitHub with Visual Studio | [Create a Git repo](https://aka.ms/vsgitlearn-1-create-repo) | 30 | 31 | ## Video Walkthrough 32 | [drawing](https://youtu.be/VlgDIqrAkGA "Syncing your Code to the Cloud") 33 | > 🎥 Click the image above for a video walkthrough of this lesson! 34 | 35 | ## How’d it Go? 36 | Congratulations! You have successfully added your project to GitHub. 37 | Please take this quick [survey](https://aka.ms/vsgitlearn-1-survey) to give use your thoughts on this lesson & challenge! 38 | 39 | ## What’s next? 40 | Now that you know how to add your own code to GitHub, you can learn advanced more advanced Git topics like branching! Check the link below to learn more: 41 | * [Create a branch in Visual Studio | Microsoft Learn](https://aka.ms/vsgitlearn-1-create-branch) 42 | -------------------------------------------------------------------------------- /4-sync-to-cloud/images/Title Card - Syncing your Code to the Cloud.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/Git-Learning-Series/869f5829fe4cb3bcb3275fc7387d04b0dccf478a/4-sync-to-cloud/images/Title Card - Syncing your Code to the Cloud.png -------------------------------------------------------------------------------- /4-sync-to-cloud/images/create-a-git-repository-window-signed-in.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/Git-Learning-Series/869f5829fe4cb3bcb3275fc7387d04b0dccf478a/4-sync-to-cloud/images/create-a-git-repository-window-signed-in.png -------------------------------------------------------------------------------- /4-sync-to-cloud/images/create-a-git-repository-window.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/Git-Learning-Series/869f5829fe4cb3bcb3275fc7387d04b0dccf478a/4-sync-to-cloud/images/create-a-git-repository-window.png -------------------------------------------------------------------------------- /4-sync-to-cloud/images/create-git-repository.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/Git-Learning-Series/869f5829fe4cb3bcb3275fc7387d04b0dccf478a/4-sync-to-cloud/images/create-git-repository.png -------------------------------------------------------------------------------- /4-sync-to-cloud/images/open-in-browser.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/Git-Learning-Series/869f5829fe4cb3bcb3275fc7387d04b0dccf478a/4-sync-to-cloud/images/open-in-browser.png -------------------------------------------------------------------------------- /4-sync-to-cloud/images/sign-in-to-github.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/Git-Learning-Series/869f5829fe4cb3bcb3275fc7387d04b0dccf478a/4-sync-to-cloud/images/sign-in-to-github.png -------------------------------------------------------------------------------- /5-daily-workflow/README.md: -------------------------------------------------------------------------------- 1 | # Daily Workflow with GitHub in Visual Studio and Next Steps 2 | In this lesson, we will learn how all the previous lessons come together in practice with the development innerloop workflow. 3 | 4 | ## Staging and Committing 5 | We talked about how to view your Git repository in Visual Studio (Committed Files), but we haven’t talked about how to commit your changes. Git has the following three main states that files can reside in: 6 | * Committed: files in your Git directory which are a part of your repository History 7 | * Staged: modified files added to the staging area in preparation for committing 8 | * Modified: modified files that haven’t been staged or committed to your repository 9 | 10 | ![Git states: modified, staged, committed](images/git-states.png) 11 | 12 | Staging files before committing them is an optional step that you might want to utilize to prepare for a commit. That way you can only commit the files that are ready to be committed (Staged). 13 | 14 |
15 | Git Changes - modified 16 | Git Changes - staged 17 | Git Changes - commit message 18 | Git Changes - committed 19 |
20 | 21 | In Visual Studio all of your modified files can be found in the Git Changes window next to Solution Explorer (view > Git Changes). You will find your modified files under the changes section. You can commit your changes right away by providing a commit message and clicking the Commit All button. Alternativly, you can chose to stage the changes that you would like to commit first using the + button. Staging can be usefull if you need to commit a subset of your changes. Once you click the commit button, you get a confirmation message and your outgoing commits status changes to 1. To view the commit you have just made, click the outgoing/incoming link which will take you the the Git Repository window. 22 | 23 | ## Pushing and Pulling 24 | Pushing is the last step once you’ve committed your staged changes. This uploads your local commits to the remote repository. 25 | 26 | Before you start a coding session, always make sure you have the most recent version of your code from your remote repository by using Fetch, Pull, or Sync. Fetching checks if there are any remote commits that you should incorporate into your local changes, pulling adds those commits to your local repo, and syncing does a Pull operation, then a Push operation. 27 | 28 | Learn more [here](https://aka.ms/vsgitlearn-1-git-fetch). 29 | 30 | ## 🚨 Challenge - Make your first commit in your repo 31 | 32 | | Challenge | Solution | Duration | What you will learn | More information | 33 | | ------------------------------- | ------------------------------- | ----------- | -------------------------------------- | --------------- | 34 | | Make a change in your new repo from last lesson, and stage, commit, and push it! | Verify if you see your change in the GitHub browser| 3 min | How to add commits to your remote repo | [Make a Git commit](https://aka.ms/vsgitlearn-1-make-commit) | 35 | 36 | ## Video Walkthrough 37 | [drawing](https://youtu.be/VlgDIqrAkGA "Daily Workflow with GitHub in Visual Studio") 38 | > 🎥 Click the image above for a video walkthrough of this lesson! 39 | 40 | ## How’d it go? 41 | You’ve reached the end of this learning series, please take this quick [survey](https://aka.ms/vsgitlearn-1-survey) to give us your thoughts on this series and what you’d like to see from us next! 42 | 43 | ## What’s next? 44 | Now that you know how to make commits, you can learn more advanced Git topics staging lines of code, amending commits, and handling merge conflicts! Check the links below to learn more: 45 | * [Stage lines of code in Visual Studio | Microsoft Learn](https://aka.ms/vsgitlearn-1-line-stage) 46 | * [Change the last commit | Microsoft Learn](https://aka.ms/vsgitlearn-1-amend) 47 | * [Resolve merge conflicts in Visual Studio | Microsoft Learn](https://aka.ms/vsgitlearn-1-resolve-conflicts) 48 | -------------------------------------------------------------------------------- /5-daily-workflow/images/Title Card - Daily Workflow with GitHub in Visual Studio.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/Git-Learning-Series/869f5829fe4cb3bcb3275fc7387d04b0dccf478a/5-daily-workflow/images/Title Card - Daily Workflow with GitHub in Visual Studio.png -------------------------------------------------------------------------------- /5-daily-workflow/images/git-changes-commit-message.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/Git-Learning-Series/869f5829fe4cb3bcb3275fc7387d04b0dccf478a/5-daily-workflow/images/git-changes-commit-message.png -------------------------------------------------------------------------------- /5-daily-workflow/images/git-changes-committed.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/Git-Learning-Series/869f5829fe4cb3bcb3275fc7387d04b0dccf478a/5-daily-workflow/images/git-changes-committed.png -------------------------------------------------------------------------------- /5-daily-workflow/images/git-changes-modified.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/Git-Learning-Series/869f5829fe4cb3bcb3275fc7387d04b0dccf478a/5-daily-workflow/images/git-changes-modified.png -------------------------------------------------------------------------------- /5-daily-workflow/images/git-changes-staged.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/Git-Learning-Series/869f5829fe4cb3bcb3275fc7387d04b0dccf478a/5-daily-workflow/images/git-changes-staged.png -------------------------------------------------------------------------------- /5-daily-workflow/images/git-states.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/Git-Learning-Series/869f5829fe4cb3bcb3275fc7387d04b0dccf478a/5-daily-workflow/images/git-states.png -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Microsoft Open Source Code of Conduct 2 | 3 | This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). 4 | 5 | Resources: 6 | 7 | - [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/) 8 | - [Microsoft Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) 9 | - Contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with questions or concerns 10 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | MIT License 2 | 3 | Copyright (c) Microsoft Corporation. 4 | 5 | Permission is hereby granted, free of charge, to any person obtaining a copy 6 | of this software and associated documentation files (the "Software"), to deal 7 | in the Software without restriction, including without limitation the rights 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 9 | copies of the Software, and to permit persons to whom the Software is 10 | furnished to do so, subject to the following conditions: 11 | 12 | The above copyright notice and this permission notice shall be included in all 13 | copies or substantial portions of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 21 | SOFTWARE 22 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | ## Getting Started with GitHub in Visual Studio 2 | Welcome to the Intro to GitHub in Visual Studio GitHub repository! We’re excited to take you along with us as we learn all about the source control. 3 | 4 | Here, you'll find a 5-part series of lessons and challenges to get you started using GitHub in Visual Studio! 5 | 6 | > **Note** 7 | > The content in this repo is part of a free, 5-part e-mail series that will teach you something new every week. The e-mails include introductions to the content in these lessons. If you came here directly and haven't signed up for the e-mails, you can do that [here](https://aka.ms/vsgitlearn-1-signup-repo) 8 | 9 | ## How-to 10 | To use this curriculum on your own, go into the numbered folders to access the lessons and projects. This series is designed to take 4 weeks, about 1 week per lesson, but feel free to complete it at your own pace. 11 | 12 | ## Lessons 13 | | | Lesson | Learning Objectives | 14 | | :-: | ------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------- | 15 | | 01 | [Welcome to the Intro to GitHub in Visual Studio Series](/1-welcome) | Introduction to Git and GitHub | 16 | | 02 | [Accessing Code in the Cloud with GitHub](/2-github) | Access code in the cloud by cloning to your local machine | 17 | | 03 | [Viewing Your Revision History in Visual Studio](/3-revision-history) | View revision history in Visual Studio with the Git repository window | 18 | | 04 | [Syncing your Code to the Cloud](/4-sync-to-cloud) | Sync your code to the cloud by pushing your commits | 19 | | 05 | [Daily Workflow with GitHub in Visual Studio and Next Steps](/5-daily-workflow) | Learn how to integrate GitHub into your daily workflow | 20 | 21 | ## Help Resources 22 | There's a few places you can go for help and more information on the topics covered in this repository. 23 | 24 | ### Documentation 25 | * [Git Experience in Visual Studio](https://aka.ms/vsgitlearn-1-git-experience) 26 | 27 | ## How to leave feedback 28 | To leave us feedback on this learning series, please fill out our [survey](https://aka.ms/vsgitlearn-1-survey) or file an issue in this repository. 29 | 30 | ## Learn More & Connect with us 31 | * [Twitter](https://twitter.com/VisualStudio) 32 | * [Youtube](https://www.youtube.com/visualstudio) 33 | * [LinkedIn](https://www.linkedin.com/showcase/microsoft-visual-studio/) 34 | -------------------------------------------------------------------------------- /SECURITY.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | ## Security 4 | 5 | Microsoft takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations, which include [Microsoft](https://github.com/Microsoft), [Azure](https://github.com/Azure), [DotNet](https://github.com/dotnet), [AspNet](https://github.com/aspnet), [Xamarin](https://github.com/xamarin), and [our GitHub organizations](https://opensource.microsoft.com/). 6 | 7 | If you believe you have found a security vulnerability in any Microsoft-owned repository that meets [Microsoft's definition of a security vulnerability](https://aka.ms/opensource/security/definition), please report it to us as described below. 8 | 9 | ## Reporting Security Issues 10 | 11 | **Please do not report security vulnerabilities through public GitHub issues.** 12 | 13 | Instead, please report them to the Microsoft Security Response Center (MSRC) at [https://msrc.microsoft.com/create-report](https://aka.ms/opensource/security/create-report). 14 | 15 | If you prefer to submit without logging in, send email to [secure@microsoft.com](mailto:secure@microsoft.com). If possible, encrypt your message with our PGP key; please download it from the [Microsoft Security Response Center PGP Key page](https://aka.ms/opensource/security/pgpkey). 16 | 17 | You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Additional information can be found at [microsoft.com/msrc](https://aka.ms/opensource/security/msrc). 18 | 19 | Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue: 20 | 21 | * Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.) 22 | * Full paths of source file(s) related to the manifestation of the issue 23 | * The location of the affected source code (tag/branch/commit or direct URL) 24 | * Any special configuration required to reproduce the issue 25 | * Step-by-step instructions to reproduce the issue 26 | * Proof-of-concept or exploit code (if possible) 27 | * Impact of the issue, including how an attacker might exploit the issue 28 | 29 | This information will help us triage your report more quickly. 30 | 31 | If you are reporting for a bug bounty, more complete reports can contribute to a higher bounty award. Please visit our [Microsoft Bug Bounty Program](https://aka.ms/opensource/security/bounty) page for more details about our active programs. 32 | 33 | ## Preferred Languages 34 | 35 | We prefer all communications to be in English. 36 | 37 | ## Policy 38 | 39 | Microsoft follows the principle of [Coordinated Vulnerability Disclosure](https://aka.ms/opensource/security/cvd). 40 | 41 | 42 | -------------------------------------------------------------------------------- /SUPPORT.md: -------------------------------------------------------------------------------- 1 | # TODO: The maintainer of this repo has not yet edited this file 2 | 3 | **REPO OWNER**: Do you want Customer Service & Support (CSS) support for this product/project? 4 | 5 | - **No CSS support:** Fill out this template with information about how to file issues and get help. 6 | - **Yes CSS support:** Fill out an intake form at [aka.ms/onboardsupport](https://aka.ms/onboardsupport). CSS will work with/help you to determine next steps. 7 | - **Not sure?** Fill out an intake as though the answer were "Yes". CSS will help you decide. 8 | 9 | *Then remove this first heading from this SUPPORT.MD file before publishing your repo.* 10 | 11 | # Support 12 | 13 | ## How to file issues and get help 14 | 15 | This project uses GitHub Issues to track bugs and feature requests. Please search the existing 16 | issues before filing new issues to avoid duplicates. For new issues, file your bug or 17 | feature request as a new Issue. 18 | 19 | For help and questions about using this project, please **REPO MAINTAINER: INSERT INSTRUCTIONS HERE 20 | FOR HOW TO ENGAGE REPO OWNERS OR COMMUNITY FOR HELP. COULD BE A STACK OVERFLOW TAG OR OTHER 21 | CHANNEL. WHERE WILL YOU HELP PEOPLE?**. 22 | 23 | ## Microsoft Support Policy 24 | 25 | Support for this **PROJECT or PRODUCT** is limited to the resources listed above. 26 | --------------------------------------------------------------------------------