{"id":9721,"date":"2013-01-30T08:49:00","date_gmt":"2013-01-30T08:49:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/visualstudioalm\/2013\/01\/30\/getting-started-with-git-in-visual-studio-and-team-foundation-service\/"},"modified":"2022-08-01T07:19:05","modified_gmt":"2022-08-01T15:19:05","slug":"getting-started-with-git-in-visual-studio-and-team-foundation-service-2","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/devops\/getting-started-with-git-in-visual-studio-and-team-foundation-service-2\/","title":{"rendered":"Getting Started with Git in Visual Studio and Team Foundation Service"},"content":{"rendered":"

By Matthew Mitrik (MS)<\/a>, Andy Lewis<\/a>, and Martin Woodward<\/a><\/p>\n

Today we announced<\/a> the availability of Git for Visual Studio and Team Foundation Service. In this post, we’ll walk through the new experiences.<\/p>\n

\n

\n Get set up:<\/strong> Get the free service<\/a>, and then you can use it with any Git client tools you want, including Visual Studio. To use the Visual Studio client tools you’ll need to install Visual Studio 2012<\/a>, apply Visual Studio 2012 Update 2 CTP<\/a>, and finally install Visual Studio Tools for Git<\/a>. You can use these client tools with any Git service you want.\n <\/p>\n<\/div>\n

Choose between TFVC and Git<\/h2>\n

With this announcement, each time you create a new team project we give you a choice: Team Foundation Version Control (TFVC) or Git? The best option for you depends on a lot of factors, including size of codebase, team size, and team distribution to name a few. Now that Git is fully integrated with TFS, the decision depends solely on what your team needs from version control. Looking at the strengths and features of each system can help make the decision easier.<\/p>\n

Team Foundation Version Control (TFVC)<\/h2>\n

TFVC is a centralized version control system. While it works well for small teams with small code bases, TFVC is capable of scaling to support very large codebases (millions of files per branch with server workspaces) and it handles large binary files well. TFVC provides very granular permission control, allowing teams to restrict access down to a file level if needed. Since all contributions are checked in to the central server, it is very easy to audit changes and identify exactly which user committed a given code change.<\/p>\n

Learn more about TFVC on MSDN<\/a>.<\/p>\n

Git<\/h2>\n

Git is a distributed version control system where each developer has a copy of the entire source repository. Having a local repository means that Git works well in environments where developers need to work without connectivity. It also offers a simple branching model that enables developers to quickly create local and private branches, enabling flexible workflows. Git also works well in modular codebases where code is distributed across many repositories.<\/p>\n

Learn more about Git on MSDN<\/a>.<\/p>\n

Ultimately, much of the decision about which version control system to use is about preference. Both systems are equally capable for the majority of teams. Make sure your team is happy with the version control system you choose.<\/p>\n

Create a Git team project in Team Foundation Service<\/h2>\n

You can quickly spin up a new Git team project with just a few clicks.<\/p>\n

\"\"
\n\"\"<\/p>\n

In the next section we’ll tell you more about how to connect to your new team project from VS. Also, we’ll talk about another option you have to begin from your local dev machine instead of from a team project.<\/p>\n

\u00a0<\/p>\n

Use Visual Studio with Git<\/h2>\n

Git provides powerful DVCS features that enable your team to collaborate on an app. But Git’s user interface can be difficult to use, and to get full value from it you may need to bring separate tools together. Visual Studio provides an integrated experience that makes it easy for your team to leverage the power of Git. And if you are a Git pro who has some favorite Git tools you still want to use, you can use them alongside Visual Studio.<\/p>\n

If your Git repository is in a TFS team project, you get additional benefits from the integration with other TFS features such as work items.\u00a0 But even if you are not using TFS, you can use Visual Studio with Git to work on a completely local repository, or to collaborate using Git hosters such as GitHub and BitBucket.<\/p>\n

To get going, connect and clone<\/h2>\n

When you are ready to begin working in your Git team project, you begin by connecting to it. Once you’ve connected to your new Git project, you’ll be prompted to Clone the repository in the team project onto your dev machine.<\/p>\n

\"\"
\n\"\"<\/p>\n

After you cloned from a Git team project, you will have two entries for this codebase, one under Team Foundation Service and one under Local Git Repositories.<\/p>\n

\"\"<\/p>\n

You can also use the tools to clone from any hosted Git repository.<\/p>\n

\"\"<\/p>\n

\u00a0<\/p>\n

\"\"<\/p>\n

Or, just start coding locally<\/h2>\n

Maybe one of the coolest features of Visual Studio with Git is that in just a few seconds, you can be writing code on a new project under local version control. Want to try it? You can create a new code project<\/a> in a new local Git repository in less than a minute:<\/p>\n

\"\"<\/p>\n

You can continue coding and committing locally for as long as you like. When you are ready to share and collaborate, just publish your code into TFS<\/a>, or into whatever Git service your team uses (e.g. CodePlex, GitHub, Bitbucket).<\/p>\n

\u00a0<\/p>\n

Customize your settings<\/h2>\n

Git associates each commit you create with your name and email address. When you first begin using Visual Studio with Git on your dev machine, if you begin by cloning from a Git team project, then Visual Studio fills these in for you.<\/p>\n

\"\"<\/p>\n

You can override the name and email settings and specify other settings.<\/p>\n

Enable download of author images from 3rd party source<\/strong>: Visual Studio can display author images on commits.\u00a0 By default it uses the image in the user’s TFS profile. If the user doesn’t have an image set, an image from Gravatar<\/a> will be used.<\/p>\n

Ignore File<\/strong>: To avoid checking in temporary non-source items such as binaries, you can specify a .gitignore file. See Ignoring files<\/a> and gitignore(5) Manual Page<\/a>.<\/p>\n

Attributes File<\/strong>: To specify options such as how the system handles line-breaks, you can specify a .gitattributes file. See Customizing Git – Git Attributes<\/a>.<\/p>\n

For more information on Git settings, see Customizing Git – Git Configuration<\/a>.<\/p>\n

Commit changes locally<\/h2>\n

As you write your code, you can commit to create a snapshot of your changes on your dev machine as often as you like. You can associate a work item with your commit by specifying its id in the comment.\u00a0<\/p>\n

\"\"
\n\"\"<\/p>\n

Later when you push your local repository to the Git team project, the commit will be associated with work item 255. In TFS you can also associate a work item with a commit after it has been pushed using the Links tab in the work item.<\/p>\n

Pull<\/h2>\n

To ensure your code integrates well with the latest code from the team, you should pull changes on a regular basis. Also, if there are any changes in the remote branch, you must pull them before you can push.<\/p>\n

Before you pull, you can fetch to see what changes are coming.<\/p>\n

\"\"<\/p>\n

When you are ready to take the changes, pull them.<\/p>\n

\"\"<\/p>\n

For step-by-step instructions, see Pull changes from the team<\/a>.<\/p>\n

Push<\/h2>\n

When you are ready to push the changes in your selected branch, just click Push.<\/p>\n

\"\"
\n\"\"<\/p>\n

For step-by-step instructions, see Push your changes<\/a>.<\/p>\n

Create and use branches<\/h2>\n

Git branches differ from TFVC branches in a few ways. Git branches are local (and thus private) until pushed. They are also more lightweight, so you can quickly create a branch on your dev machine whenever you need one.<\/p>\n

\"\"
\n\"\"<\/p>\n

You can switch the branch you are working in from Changes and Commits pages.<\/p>\n

\"\"<\/p>\n

When you are ready, you merge to combine the work.<\/p>\n

\"\"
\n\"\"<\/p>\n

For more details on how branches work in Git, see Git Branching<\/a>.<\/p>\n

Resolve conflicts<\/h2>\n

Sometimes you will need to resolve conflicts before you can complete a pull or a merge.<\/p>\n

\"\"<\/p>\n

Visual Studio makes it easy for you to resolve some of the most common kinds of conflicts, such as content conflicts.<\/p>\n

\"\"
\n\"\"<\/p>\n

Some conflicts (such as rename conflicts) must be resolved using a command-line tool such as Msysgit<\/a>.<\/p>\n

View History<\/h2>\n

You can view the history of an item from Solution Explorer or from the Changes page. You can also view the history of an entire branch from the Branches page.<\/p>\n

\"\"<\/p>\n

Web Access<\/h2>\n

After commits have been pushed into the repo, the Code hub starts to look a lot more interesting.<\/p>\n

Explorer view<\/h2>\n

The Explorer view is the center of the browse experience in the web. You can drill in to the contents of a repository and see the commit message and author of the latest changes to each folder and file.<\/p>\n

\"\"<\/p>\n

History<\/h3>\n

As you’re exploring the repo, you can easily switch to the History view to view the history of a file or folder. The history view is a similar to the VS view, providing the comment, author, and time of the commit. Off to the left is an indicator showing relative size of each commit.<\/p>\n

\"\"<\/p>\n

Compare files<\/h3>\n

Using the Compare view, you can compare versions of a file in either a side-by-side or inline diff view, complete with syntax highlighting.<\/p>\n

\"\"<\/p>\n

Commits view<\/h2>\n

To see an all-up view of the repo history, use the commits view. By default, the view shows all changes, but you can filter to view just your commits, or use the Advanced search to filter down the list by author, path, and\/or date.<\/p>\n

\"\"<\/p>\n

Commit Details<\/h3>\n

Drilling in on a commit shows the detailed metadata for the commit, including associated work items. Each file modified in the commit is also shown with an inline diff to summarize the changes.<\/p>\n

\"\"<\/p>\n

Pivot on branch or tag<\/h2>\n

In any of the views in the Code hub, the branch selector may be used to pivot the entire repo view by branch. If you’ve pushed any tags to the repo, they’ll be shown in the same picker.<\/p>\n

\"\"<\/p>\n

Xcode<\/h2>\n

Developers using Xcode will be able to use the existing Git integration to work with repos hosted in Team Foundation Service. Be sure to enable alternate credentials<\/a> (basic auth) for your TF Service user profile before trying to push and pull from Xcode (or any other third party Git client for that matter). Note that you can get the clone URL from the Explore view in the project’s web portal.<\/p>\n

\"\"<\/p>\n

Team Foundation Build and Git<\/h2>\n

The cloud build service can be used to build Git projects much like you can build TFVC projects.<\/p>\n

Configure a manual build<\/h2>\n

Configuring a build for Git projects is similar to configuring TFVC builds. You can start by clicking New Build Definition in the Builds page in Team Explorer.<\/p>\n

\"\"<\/p>\n

In the build definition editor, give your build a name and a description. On the process page specify the branch you want to build and the relative path to the solution file to build. Note that only the manual trigger is currently available, but we’re working on adding more.<\/p>\n

\"\"<\/p>\n

Queue a new build from the Builds page. Remember, you need to push your commits to the service in order to build them.<\/p>\n

\"\"<\/p>\n

Build report<\/h2>\n

After the build has completed, the build report shows that the build succeeded.<\/p>\n

\"\"<\/p>\n

Next steps<\/h2>\n

Downloads<\/h2>\n