Elevate Your Git and GitHub Skills in Visual Studio with the Intermediate and Advanced Series

Jessie Houghton

Git and Version Control skills are essential for development, but they’re often glossed over in coding curriculum and onboarding. We often memorize a few commands without understanding how to recover from sticky situations or leverage Git to the fullest. Are you ready to take your GitHub knowledge to the next level within Visual Studio? After the success of our introductory email learning series, we’re excited to announce our upcoming intermediate and advanced video series designed to enhance your Git and GitHub expertise. These videos are each less than 5 minutes long, and they are designed to help you get the most out of the Git integration in Visual Studio.

Branch Out with Confidence

Creating and Leveraging Branches: Discover the power of branching in Git and learn how to create, manage, and leverage branches to streamline your development workflow in Visual Studio.

Air Date: 1/15/24

Seamless Workflow Integration

Workflow with GitHub: Dive deeper into the integrated GitHub experience in Visual Studio. We’ll you through the seamless workflow that helps you stay productive and focused on coding.

Air Date: 1/22/24

Mastering Merge Conflicts

Handling Conflicts with Merges: Merge conflicts can be daunting, but they don’t have to be. Visual Studio has an intuitive UI to help you resolve conflicts and avoid mistakes.

Air Date: 1/29/24

Recover Like a Pro

Recovering from Mistakes: Everyone makes mistakes, but not everyone knows how to recover from them gracefully. Learn how to errors and get back on track with Git’s powerful tools in Visual Studio.

Air Date: 2/5/24

Apply Specific Changes

Cherry Picking in the Visual Studio Git Repository Window: Need a commit from another branch, but don’t want to merge the whole thing? Learn how to cherry-pick commits with the help of the multi-branch Git graph.

Air Date: 2/12/24

Combine Branches with Ease

Branches: Merging, Rebasing, and Squashing in Visual Studio and GitHub: Understand the differences between different merge methods and how to apply them in Visual Studio and when completing pull request on GitHub.

Air Date: 2/19/24

Never Lose Your Progress

Saving Work in Progress with Stashing in Visual Studio: Context switching is painful. Learn how stashing can help you keep your work in progress safe when switching branches.

Air Date: 2/26/24

Reverse the Clock

Going Back in Time with Git Blame and Annotate in Visual Studio: Confused about a line of code or a method? Turn back the clock to find out when the code was committed, by who, and why.

Air Date: 3/4/24

Learn intermediate and advanced Git topics as we delve into these topics with practical examples. You’ll enhance your skills, boost your productivity, and master Git and GitHub in Visual Studio.

Engage with Us

We appreciate the time you’ve spent reporting issues/suggestions and hope you continue to give us feedback when using Visual Studio on what you like and what we can improve. Your feedback is critical to help us make Visual Studio the best tool it can be! You can share feedback with us via Developer Community: report any bugs or issues via report a problem and share your suggestions for new features or improvements to existing ones.

Stay connected with the Visual Studio team by following us on YouTube, Twitter, LinkedIn, Twitch and on Microsoft Learn.









Discussion is closed. Login to edit/delete existing comments.

  • Carl John Dennis Aguinaldo 1

    Awesome video series. Looking forward to the next. However, I do want to point out that the air date still says 2023 instead of 2024. I’m not sure if that is intentional or not.

    Thanks for the content!

    • Jessie HoughtonMicrosoft employee 1

      Great catch! The post has been updated accordingly.

  • Sejin Yoon 0

    Great series thank you !

  • Peter Nimmo 0

    For people stuck with TFS, it would be really useful if you added a branch to Git option, that would allow you to start working on a feature from the current code in TFS.

    So it would basically branch the current code into a Git repository and then once you’ve finished developing the feature in the Git copy of the branch that you would then be able to merge it back into TFS.

    Without this it is very hard because you can only diff from the previous checkin, you cannot diff part way through your coding of the new feature, and you can’t commit early and often because TFS is the live branch.

    Also note the TFS support conflicts with .editorconfig, if you write an .editorconfig in either VS2022 or VS2015 it always triggers a checkout of every single project file in your solution for no reason, and it locks up Visual Studio until they have all been checked out.

Feedback usabilla icon