0

I've noticed a buzz word "we should use Git for TFS". My understanding is that Git is just DVCS.

TFS support everything from branching, labelling, merging, checking in, checking out, shelving, etc.

Could someone please help me understand under what scenarios should team use Git or TFS?

Apart from local repository and distributed, what other benefits can it provide to the team?

Does it have better support of branching and merging? From what I've seen developer can create new branches on his/her local repository, which I think should make more hard to manage branches.

Any suggestions will be good.

Biffen
  • 6,249
  • 6
  • 28
  • 36
Nil Pun
  • 17,035
  • 39
  • 172
  • 294
  • 1
    Too broad and offtopic. – Sergio Tulentsev Jun 09 '14 at 09:10
  • 2
    Speed. Seriously, don't underestimate it as a benefit. It completely changes how you see code. For example, with Git merging 6 times a day is painless. That doesn't mean that people using git merge 6 or 10 times a day but the thought of doing that doesn't scare people as much as with other source control software. Once branches don't scare you anymore then there's no need to "manage" all branches. Another example is debugging, because of it's speed you will start using git more and more as a tool to read code (find out why the code was written that way). – slebetman Jun 09 '14 at 09:17
  • comparing Git to TFS is like comparing an editor to an IDE. An IDE _is_ an editor but depending on your point of view either a) a very bloated one that's too slow b) a feature rich editor that does more things than _just_ an editor. All the benefits you mention for TFS are things Git does (very, very well). – AD7six Jun 09 '14 at 09:36
  • Incidentally it's funny to see Git referred to as Gits – AD7six Jun 09 '14 at 09:39

1 Answers1

2

TFS support everything from branching, labelling, merging, checkin, checkout, shelve etc.

Those are features that any VCS (Version Control System) does support. Git supports those as well (shelve is called git stash: see "what's the Git equivalent of TFS commands shelve/unshelve? cherry-pick?" and "git stash equivalents in other revision control systems?").

As I explained in "In what ways is Mercurial better/worse than TFS?", TFS is a ALM (Application Lifecycle Management) tool, with tickets, reporting, project tracking and more), in addition of the simple VCS features.

See also "Which version control system should I use?", mentioned in "Git vs TFVC Source Control".

With offers like git-tf, you can integrate Git to TFS anyway.
VS2013 supports Git as well, although you need to tweak it to view the TFS work items.

Things start getting interesting if one could have Git as their source control with Team Foundation on the backend for ALM tools.

Community
  • 1
  • 1
VonC
  • 1,262,500
  • 529
  • 4,410
  • 5,250