This project is read-only.

--deep option with when gated checkins are enabled on the build?

Sep 24, 2013 at 4:20 PM
Guys i love this tool. It has totally revolutionized the way i work. One thing that i would love that has never worked for me is the --deep option when pushing my changes to TFS. I think it might be due the build being a gated checkin build. I work to keep the commits really nice and clean and then when i checkin to TFS its always one commit no matter what i do. Am i right that the gated check-in is whats causing git-tf to checkin as one commit? Anyway to get around this?

Sep 25, 2013 at 4:28 PM

Do you mean that all your commits are merged and checked in as a single change set on the TFS server?

Sep 27, 2013 at 1:45 PM
Edited Sep 27, 2013 at 1:46 PM
Yep thats exactly what i meant Alex

Sep 27, 2013 at 4:32 PM

I haven't found any evidence in the Git-TF code that it might change --deep/--shallow option depending on gated check-in build. Could you provide us with some additional information?
  1. The Git-TF version you use (run git tf --version command)
  2. The exact command line used
  3. Git config files local/global
Feel free to use my personal e-mail for that:

Also it would be helpful if you could collect and send us a detailed log of a command run reproducing that issue. Please let me know if that is feasible, and I'll provide you with instructions on how to do that.