Checkin

git tf checkin [--deep]

Checks in the changes made in the Git repo into TFS. By default, the checkin command will create a single TFS changeset for the aggregate of all changes made on the current branch in Git since the last checkin to TFS. When used with the --deep option, a TFS changeset will be created for each Git commit on the current branch since the last checkin to TFS.

Last edited Aug 9, 2012 at 9:49 PM by mmitrik, version 1

Comments

brianlow May 6 at 5:03 PM 
I believe the --deep option is enabled by default if you cloned your repository with --deep.

brianlow Jan 16 at 8:23 PM 
--renamemode=all
--renamemode=justfiles (this is the default in v2.0.1 release Jan 8, 2013)

Affects folder renames but not sure exactly how.

weisjohn Jan 14 at 1:45 AM 
can you add some docs here surrounding what happens on a successful checkin?

I stumbled across this on a repo that I'm working on, are these only made if a successful checkin happens?:

```
$ git tag
TFS_C32171
TFS_C32319
TFS_C32320
TFS_C32321
TFS_C32322
```

sstude Nov 18, 2012 at 7:56 PM 
Looks like --associate works only for last checkin, because all previous checkins are not associated with the TFS item.

pmiossec Oct 1, 2012 at 1:09 PM 
For the information, you could associate and resolve workitems with the command line options :
--resolve=<workitem id>
ID of the TFS work item to resolve during check-in
--associate=<workitem id>
ID of the TFS work item to associate during check-in