UNPKG

tfs

Version:

NodeJS wrapper for Team Foundation Source Control CLI.

3,826 lines (924 loc) 74.5 kB
<!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <title>JSDoc: Global</title> <script src="scripts/prettify/prettify.js"> </script> <script src="scripts/prettify/lang-css.js"> </script> <!--[if lt IE 9]> <script src="//html5shiv.googlecode.com/svn/trunk/html5.js"></script> <![endif]--> <link type="text/css" rel="stylesheet" href="styles/prettify-tomorrow.css"> <link type="text/css" rel="stylesheet" href="styles/jsdoc-default.css"> </head> <body> <div id="main"> <h1 class="page-title">Global</h1> <section> <header> <h2></h2> </header> <article> <div class="container-overview"> <dl class="details"> </dl> </div> <h3 class="subsection-title">Members</h3> <h4 class="name" id="debug"><span class="type-signature"></span>debug<span class="type-signature"> :Object</span></h4> <div class="description"> [debug description] </div> <h5>Type:</h5> <ul> <li> <span class="param-type">Object</span> </li> </ul> <dl class="details"> <dt class="tag-version">Version:</dt> <dd class="tag-version"><ul class="dummy"><li>1.2.7</li></ul></dd> <dt class="tag-source">Source:</dt> <dd class="tag-source"><ul class="dummy"><li> <a href="utils_debug.js.html">utils/debug.js</a>, <a href="utils_debug.js.html#line15">line 15</a> </li></ul></dd> <dt class="tag-todo">To Do:</dt> <dd class="tag-todo"> <ul> <li>Comment debug.js</li> </ul> </dd> </dl> <h4 class="name" id="format"><span class="type-signature"></span>format<span class="type-signature"> :Object</span></h4> <div class="description"> Formatting functions </div> <h5>Type:</h5> <ul> <li> <span class="param-type">Object</span> </li> </ul> <dl class="details"> <dt class="tag-source">Source:</dt> <dd class="tag-source"><ul class="dummy"><li> <a href="utils_format.js.html">utils/format.js</a>, <a href="utils_format.js.html#line8">line 8</a> </li></ul></dd> </dl> <h4 class="name" id="output"><span class="type-signature"></span>output<span class="type-signature"> :Object</span></h4> <div class="description"> [output description] </div> <h5>Type:</h5> <ul> <li> <span class="param-type">Object</span> </li> </ul> <dl class="details"> <dt class="tag-version">Version:</dt> <dd class="tag-version"><ul class="dummy"><li>1.3.2</li></ul></dd> <dt class="tag-source">Source:</dt> <dd class="tag-source"><ul class="dummy"><li> <a href="utils_output.js.html">utils/output.js</a>, <a href="utils_output.js.html#line12">line 12</a> </li></ul></dd> <dt class="tag-todo">To Do:</dt> <dd class="tag-todo"> <ul> <li>Comment output.js</li> </ul> </dd> </dl> <h3 class="subsection-title">Methods</h3> <h4 class="name" id="_delete"><span class="type-signature"></span>_delete<span class="signature">(itemspec, options)</span><span class="type-signature"></span></h4> <div class="description"> Removes files and folders from the Team Foundation version control server and deletes them from the disk.Note The results of this command are not visible in other workspaces until you perform a check-in operation. For more information, see Check In Pending Changes.Required PermissionsTo use the delete command, you must have the Check out permission set to Allow. If you include the /lock option with a value other than none, you must have the Lock permission set to Allow. Additionally, you must own the workspace or have the global Administer workspaces permission set to Allow. For more information, see Team Foundation Server Permissions. </div> <h5>Parameters:</h5> <table class="params"> <thead> <tr> <th>Name</th> <th>Type</th> <th class="last">Description</th> </tr> </thead> <tbody> <tr> <td class="name"><code>itemspec</code></td> <td class="type"> <span class="param-type">Array</span> </td> <td class="description last">File(s) or folder(s) to retrieve. If null/undefined, equals CWD.</td> </tr> <tr> <td class="name"><code>options</code></td> <td class="type"> <span class="param-type">Object</span> </td> <td class="description last">Command options</td> </tr> </tbody> </table> <dl class="details"> <dt class="tag-source">Source:</dt> <dd class="tag-source"><ul class="dummy"><li> <a href="tfs_delete.js.html">tfs/delete.js</a>, <a href="tfs_delete.js.html#line12">line 12</a> </li></ul></dd> </dl> <h4 class="name" id="branch"><span class="type-signature"></span>branch<span class="signature">(itemspec, options)</span><span class="type-signature"></span></h4> <div class="description"> The branch command copies an item or set of items, including metadata and version control history, from one location to another in the Team Foundation version control server and in the local workspace.NoteThe results of this command are not reflected in the Team Foundation version control server until you perform a check-in operation. For more information, see Check In Pending Changes.Required PermissionsTo use the branch command, you must have the Read permission for the source item and the Check out and Merge permissions for the target folder set to Allow. For more information, see Team Foundation Server Permissions. </div> <h5>Parameters:</h5> <table class="params"> <thead> <tr> <th>Name</th> <th>Type</th> <th class="last">Description</th> </tr> </thead> <tbody> <tr> <td class="name"><code>itemspec</code></td> <td class="type"> <span class="param-type">Array</span> </td> <td class="description last">File(s) or folder(s) to retrieve. If null/undefined, equals CWD.</td> </tr> <tr> <td class="name"><code>options</code></td> <td class="type"> <span class="param-type">Object</span> </td> <td class="description last">Command options</td> </tr> </tbody> </table> <dl class="details"> <dt class="tag-source">Source:</dt> <dd class="tag-source"><ul class="dummy"><li> <a href="tfs_branch.js.html">tfs/branch.js</a>, <a href="tfs_branch.js.html#line12">line 12</a> </li></ul></dd> </dl> <h4 class="name" id="branches"><span class="type-signature"></span>branches<span class="signature">(itemspec, options)</span><span class="type-signature"></span></h4> <div class="description"> Displays the history of a branch for a specified file or folder.Required PermissionsTo use the branches command, your Read permission must be set to Allow for the item and any branches to view their history. For more information, see Team Foundation Server Permissions. </div> <h5>Parameters:</h5> <table class="params"> <thead> <tr> <th>Name</th> <th>Type</th> <th class="last">Description</th> </tr> </thead> <tbody> <tr> <td class="name"><code>itemspec</code></td> <td class="type"> <span class="param-type">Array</span> </td> <td class="description last">File(s) or folder(s) to retrieve. If null/undefined, equals CWD.</td> </tr> <tr> <td class="name"><code>options</code></td> <td class="type"> <span class="param-type">Object</span> </td> <td class="description last">Command options</td> </tr> </tbody> </table> <dl class="details"> <dt class="tag-source">Source:</dt> <dd class="tag-source"><ul class="dummy"><li> <a href="tfs_branches.js.html">tfs/branches.js</a>, <a href="tfs_branches.js.html#line12">line 12</a> </li></ul></dd> </dl> <h4 class="name" id="buildSettings"><span class="type-signature"></span>buildSettings<span class="signature">()</span><span class="type-signature"></span></h4> <div class="description"> Look for TFS command line tool and create settings file </div> <dl class="details"> <dt class="tag-source">Source:</dt> <dd class="tag-source"><ul class="dummy"><li> <a href="setup.js.html">setup.js</a>, <a href="setup.js.html#line38">line 38</a> </li></ul></dd> </dl> <h4 class="name" id="changeset"><span class="type-signature"></span>changeset<span class="signature">(itemspec, options)</span><span class="type-signature"></span></h4> <div class="description"> Displays information about and lets you change the attributes, such as comments and check-in notes, that are associated with a changeset.Required PermissionsTo use the changeset command you must have the Read permission set to Allow for any files or folders in the changeset for which you wish to display full information. The only users who can modify the notes and comments that are associated with a changeset are the users who created the changeset or a user who has the Revise other user\'s changes global permission. For more information, see Team Foundation Server Permissions. </div> <h5>Parameters:</h5> <table class="params"> <thead> <tr> <th>Name</th> <th>Type</th> <th class="last">Description</th> </tr> </thead> <tbody> <tr> <td class="name"><code>itemspec</code></td> <td class="type"> <span class="param-type">Array</span> </td> <td class="description last">File(s) or folder(s) to retrieve. If null/undefined, equals CWD.</td> </tr> <tr> <td class="name"><code>options</code></td> <td class="type"> <span class="param-type">Object</span> </td> <td class="description last">Command options</td> </tr> </tbody> </table> <dl class="details"> <dt class="tag-source">Source:</dt> <dd class="tag-source"><ul class="dummy"><li> <a href="tfs_changeset.js.html">tfs/changeset.js</a>, <a href="tfs_changeset.js.html#line12">line 12</a> </li></ul></dd> </dl> <h4 class="name" id="configure"><span class="type-signature"></span>configure<span class="signature">(itemspec, options)</span><span class="type-signature"></span></h4> <div class="description"> Enables an administrator to view and change the following configuration settings for a team project in the Source Control Settings dialog box:Check-out settingsCheck-in policiesCheck-in notesRequired PermissionsTo use the configure command, you must have the Edit server-level information permission set to Allow. For more information, see Team Foundation Server Permissions. </div> <h5>Parameters:</h5> <table class="params"> <thead> <tr> <th>Name</th> <th>Type</th> <th class="last">Description</th> </tr> </thead> <tbody> <tr> <td class="name"><code>itemspec</code></td> <td class="type"> <span class="param-type">Array</span> </td> <td class="description last">File(s) or folder(s) to retrieve. If null/undefined, equals CWD.</td> </tr> <tr> <td class="name"><code>options</code></td> <td class="type"> <span class="param-type">Object</span> </td> <td class="description last">Command options</td> </tr> </tbody> </table> <dl class="details"> <dt class="tag-source">Source:</dt> <dd class="tag-source"><ul class="dummy"><li> <a href="tfs_configure.js.html">tfs/configure.js</a>, <a href="tfs_configure.js.html#line12">line 12</a> </li></ul></dd> </dl> <h4 class="name" id="destroy"><span class="type-signature"></span>destroy<span class="signature">(itemspec, options)</span><span class="type-signature"></span></h4> <div class="description"> Use the tfSync destroy command to destroy, or permanently delete, version-controlled files from Team Foundation version control. The destroy action cannot be reversed. You must not destroy files that are still needed. Sometimes you have to clean up version control systems. For example, if some files are infected with a computer virus, you have to remove them permanently from version control.Before you run tf destroy without the /keephistory option, we recommend that you first delete the files you want to destroy. For more information, see Delete Files and Folders from Version Control.After you delete the files you can synchronize the Team Foundation warehouse. Otherwise, the warehouse will not be synchronized with the destroyed items.Required PermissionsTo use the destroy command, you must belong to the Team Foundation Administrators security group. For more information, see Team Foundation Server Permissions. </div> <h5>Parameters:</h5> <table class="params"> <thead> <tr> <th>Name</th> <th>Type</th> <th class="last">Description</th> </tr> </thead> <tbody> <tr> <td class="name"><code>itemspec</code></td> <td class="type"> <span class="param-type">Array</span> </td> <td class="description last">File(s) or folder(s) to retrieve. If null/undefined, equals CWD.</td> </tr> <tr> <td class="name"><code>options</code></td> <td class="type"> <span class="param-type">Object</span> </td> <td class="description last">Command options</td> </tr> </tbody> </table> <dl class="details"> <dt class="tag-source">Source:</dt> <dd class="tag-source"><ul class="dummy"><li> <a href="tfs_destroy.js.html">tfs/destroy.js</a>, <a href="tfs_destroy.js.html#line12">line 12</a> </li></ul></dd> </dl> <h4 class="name" id="diff"><span class="type-signature"></span>diff<span class="signature">(itemspec, options)</span><span class="type-signature"></span></h4> <div class="description"> Compares, and if it is possible, displays differences between two files, files in two folders, or a shelveset and a local or a server file.Required PermissionsTo use the difference command, you must have the Read permission for all specified items set to Allow. For more information, see Team Foundation Server Permissions. </div> <h5>Parameters:</h5> <table class="params"> <thead> <tr> <th>Name</th> <th>Type</th> <th class="last">Description</th> </tr> </thead> <tbody> <tr> <td class="name"><code>itemspec</code></td> <td class="type"> <span class="param-type">Array</span> </td> <td class="description last">File(s) or folder(s) to retrieve. If null/undefined, equals CWD.</td> </tr> <tr> <td class="name"><code>options</code></td> <td class="type"> <span class="param-type">Object</span> </td> <td class="description last">Command options</td> </tr> </tbody> </table> <dl class="details"> <dt class="tag-source">Source:</dt> <dd class="tag-source"><ul class="dummy"><li> <a href="tfs_diff.js.html">tfs/diff.js</a>, <a href="tfs_diff.js.html#line12">line 12</a> </li></ul></dd> </dl> <h4 class="name" id="dir"><span class="type-signature"></span>dir<span class="signature">(itemspec, options)</span><span class="type-signature"></span></h4> <div class="description"> The dir command displays all or some of the contents of the server for Team Foundation version control.Required PermissionsTo use the dir command, you must have Read permission set to Allow. For more information, see Team Foundation Server Permissions. </div> <h5>Parameters:</h5> <table class="params"> <thead> <tr> <th>Name</th> <th>Type</th> <th class="last">Description</th> </tr> </thead> <tbody> <tr> <td class="name"><code>itemspec</code></td> <td class="type"> <span class="param-type">Array</span> </td> <td class="description last">File(s) or folder(s) to retrieve. If null/undefined, equals CWD.</td> </tr> <tr> <td class="name"><code>options</code></td> <td class="type"> <span class="param-type">Object</span> </td> <td class="description last">Command options</td> </tr> </tbody> </table> <dl class="details"> <dt class="tag-source">Source:</dt> <dd class="tag-source"><ul class="dummy"><li> <a href="tfs_dir.js.html">tfs/dir.js</a>, <a href="tfs_dir.js.html#line12">line 12</a> </li></ul></dd> </dl> <h4 class="name" id="fileExists"><span class="type-signature"></span>fileExists<span class="signature">(filePath, isDirectory)</span><span class="type-signature"> &rarr; {Boolean}</span></h4> <div class="description"> [fileExists description] </div> <h5>Parameters:</h5> <table class="params"> <thead> <tr> <th>Name</th> <th>Type</th> <th class="last">Description</th> </tr> </thead> <tbody> <tr> <td class="name"><code>filePath</code></td> <td class="type"> <span class="param-type">String</span> </td> <td class="description last">File path</td> </tr> <tr> <td class="name"><code>isDirectory</code></td> <td class="type"> <span class="param-type">Boolean</span> </td> <td class="description last">Check if it's a directory</td> </tr> </tbody> </table> <dl class="details"> <dt class="tag-version">Version:</dt> <dd class="tag-version"><ul class="dummy"><li>1.2.3</li></ul></dd> <dt class="tag-source">Source:</dt> <dd class="tag-source"><ul class="dummy"><li> <a href="utils_fileExists.js.html">utils/fileExists.js</a>, <a href="utils_fileExists.js.html#line15">line 15</a> </li></ul></dd> <dt class="tag-todo">To Do:</dt> <dd class="tag-todo"> <ul> <li>Comment fileExists.js</li> </ul> </dd> </dl> <h5>Returns:</h5> <div class="param-desc"> Return TRUE if file exists (and is a directory) </div> <dl> <dt> Type </dt> <dd> <span class="param-type">Boolean</span> </dd> </dl> <h4 class="name" id="folderdiff"><span class="type-signature"></span>folderdiff<span class="signature">(itemspec, options)</span><span class="type-signature"></span></h4> <div class="description"> Use the folderdiff command to display and compare a visual representation of the differences between files in two server folders, in a server folder and a local folder, or in two local folders. Required PermissionsTo use the folderdiff command, you must have the Read permission set to Allow. For more information, see Team Foundation Server Permissions. </div> <h5>Parameters:</h5> <table class="params"> <thead> <tr> <th>Name</th> <th>Type</th> <th class="last">Description</th> </tr> </thead> <tbody> <tr> <td class="name"><code>itemspec</code></td> <td class="type"> <span class="param-type">Array</span> </td> <td class="description last">File(s) or folder(s) to retrieve. If null/undefined, equals CWD.</td> </tr> <tr> <td class="name"><code>options</code></td> <td class="type"> <span class="param-type">Object</span> </td> <td class="description last">Command options</td> </tr> </tbody> </table> <dl class="details"> <dt class="tag-source">Source:</dt> <dd class="tag-source"><ul class="dummy"><li> <a href="tfs_folderdiff.js.html">tfs/folderdiff.js</a>, <a href="tfs_folderdiff.js.html#line12">line 12</a> </li></ul></dd> </dl> <h4 class="name" id="label"><span class="type-signature"></span>label<span class="signature">(itemspec, options)</span><span class="type-signature"></span></h4> <div class="description"> Attaches a label to or removes a label from a version of a file or folder in the server for Team Foundation version control.Required PermissionsTo use the label command, you must have the Label permission set to Allow. To modify or delete labels created by other users, you must have the Administer labels permission set to Allow. For more information, see Team Foundation Server Permissions. </div> <h5>Parameters:</h5> <table class="params"> <thead> <tr> <th>Name</th> <th>Type</th> <th class="last">Description</th> </tr> </thead> <tbody> <tr> <td class="name"><code>itemspec</code></td> <td class="type"> <span class="param-type">Array</span> </td> <td class="description last">File(s) or folder(s) to retrieve. If null/undefined, equals CWD.</td> </tr> <tr> <td class="name"><code>options</code></td> <td class="type"> <span class="param-type">Object</span> </td> <td class="description last">Command options</td> </tr> </tbody> </table> <dl class="details"> <dt class="tag-source">Source:</dt> <dd class="tag-source"><ul class="dummy"><li> <a href="tfs_label.js.html">tfs/label.js</a>, <a href="tfs_label.js.html#line12">line 12</a> </li></ul></dd> </dl> <h4 class="name" id="labels"><span class="type-signature"></span>labels<span class="signature">(itemspec, options)</span><span class="type-signature"></span></h4> <div class="description"> Displays the list of labels in the server for Team Foundation version control.Required PermissionsTo use the labels command, you must have the Read permission set to Allow for all files or folders to which the specified label is attached. If you have permission to some, but not all the files referenced in the label, partial results are displayed. For more information, see Team Foundation Server Permissions. </div> <h5>Parameters:</h5> <table class="params"> <thead> <tr> <th>Name</th> <th>Type</th> <th class="last">Description</th> </tr> </thead> <tbody> <tr> <td class="name"><code>itemspec</code></td> <td class="type"> <span class="param-type">Array</span> </td> <td class="description last">File(s) or folder(s) to retrieve. If null/undefined, equals CWD.</td> </tr> <tr> <td class="name"><code>options</code></td> <td class="type"> <span class="param-type">Object</span> </td> <td class="description last">Command options</td> </tr> </tbody> </table> <dl class="details"> <dt class="tag-source">Source:</dt> <dd class="tag-source"><ul class="dummy"><li> <a href="tfs_labels.js.html">tfs/labels.js</a>, <a href="tfs_labels.js.html#line12">line 12</a> </li></ul></dd> </dl> <h4 class="name" id="localversions"><span class="type-signature"></span>localversions<span class="signature">(itemspec, options)</span><span class="type-signature"></span></h4> <div class="description"> Displays the version of one or more items in a workspace.Required PermissionsTo use the localversions command, you must have the Use permission to the workspace. For more information, see Team Foundation Server Permissions. </div> <h5>Parameters:</h5> <table class="params"> <thead> <tr> <th>Name</th> <th>Type</th> <th class="last">Description</th> </tr> </thead> <tbody> <tr> <td class="name"><code>itemspec</code></td> <td class="type"> <span class="param-type">Array</span> </td> <td class="description last">File(s) or folder(s) to retrieve. If null/undefined, equals CWD.</td> </tr> <tr> <td class="name"><code>options</code></td> <td class="type"> <span class="param-type">Object</span> </td> <td class="description last">Command options</td> </tr> </tbody> </table> <dl class="details"> <dt class="tag-source">Source:</dt> <dd class="tag-source"><ul class="dummy"><li> <a href="tfs_localversions.js.html">tfs/localversions.js</a>, <a href="tfs_localversions.js.html#line12">line 12</a> </li></ul></dd> </dl> <h4 class="name" id="lock"><span class="type-signature"></span>lock<span class="signature">(itemspec, options)</span><span class="type-signature"></span></h4> <div class="description"> Locks or unlocks a file or folder to deny or restore the right of users to check out an item for edit into a different workspace or to check in pending changes to an item from a different workspace.Required PermissionsTo use the lock command, you must have the Lock permission set to Allow. Having the Unlock other user\'s changes permission set to Allow is required to remove a lock held by another user if you do not have Write permission for that user\'s workspace. For more information, see Team Foundation Server Permissions. </div> <h5>Parameters:</h5> <table class="params"> <thead> <tr> <th>Name</th> <th>Type</th> <th class="last">Description</th> </tr> </thead> <tbody> <tr> <td class="name"><code>itemspec</code></td> <td class="type"> <span class="param-type">Array</span> </td> <td class="description last">File(s) or folder(s) to retrieve. If null/undefined, equals CWD.</td> </tr> <tr> <td class="name"><code>options</code></td> <td class="type"> <span class="param-type">Object</span> </td> <td class="description last">Command options</td> </tr> </tbody> </table> <dl class="details"> <dt class="tag-source">Source:</dt> <dd class="tag-source"><ul class="dummy"><li> <a href="tfs_lock.js.html">tfs/lock.js</a>, <a href="tfs_lock.js.html#line12">line 12</a> </li></ul></dd> </dl> <h4 class="name" id="merge"><span class="type-signature"></span>merge<span class="signature">(itemspec, options)</span><span class="type-signature"></span></h4> <div class="description"> The merge command applies changes from one branch into another.NoteThe results of this command are not reflected in the Team Foundation version control server until you perform a check-in operation. For more information, see Check In Pending Changes.Required PermissionsTo use the merge command, you must have the Check out permission set to Allow for the workspace folder that contains the destination and you must have the Read permission set to Allow for the workspace folder that contains the source. For more information, see Team Foundation Server Permissions. </div> <h5>Parameters:</h5> <table class="params"> <thead> <tr> <th>Name</th> <th>Type</th> <th class="last">Description</th> </tr> </thead> <tbody> <tr> <td class="name"><code>itemspec</code></td> <td class="type"> <span class="param-type">Array</span> </td> <td class="description last">File(s) or folder(s) to retrieve. If null/undefined, equals CWD.</td> </tr> <tr> <td class="name"><code>options</code></td> <td class="type"> <span class="param-type">Object</span> </td> <td class="description last">Command options</td> </tr> </tbody> </table> <dl class="details"> <dt class="tag-source">Source:</dt> <dd class="tag-source"><ul class="dummy"><li> <a href="tfs_merge.js.html">tfs/merge.js</a>, <a href="tfs_merge.js.html#line12">line 12</a> </li></ul></dd> </dl> <h4 class="name" id="merges"><span class="type-signature"></span>merges<span class="signature">(itemspec, options)</span><span class="type-signature"></span></h4> <div class="description"> Displays detailed information about past merges between the specified source and destination branches.Required PermissionsTo use the merges command, you must have the Read permission set to Allow for both source and destination branches. For more information, see Team Foundation Server Permissions. </div> <h5>Parameters:</h5> <table class="params"> <thead> <tr> <th>Name</th> <th>Type</th> <th class="last">Description</th> </tr> </thead> <tbody> <tr> <td class="name"><code>itemspec</code></td> <td class="type"> <span class="param-type">Array</span> </td> <td class="description last">File(s) or folder(s) to retrieve. If null/undefined, equals CWD.</td> </tr> <tr> <td class="name"><code>options</code></td> <td class="type"> <span class="param-type">Object</span> </td> <td class="description last">Command options</td> </tr> </tbody> </table> <dl class="details"> <dt class="tag-source">Source:</dt> <dd class="tag-source"><ul class="dummy"><li> <a href="tfs_merges.js.html">tfs/merges.js</a>, <a href="tfs_merges.js.html#line12">line 12</a> </li></ul></dd> </dl> <h4 class="name" id="permission"><span class="type-signature"></span>permission<span class="signature">(itemspec, options)</span><span class="type-signature"></span></h4> <div class="description"> Modifies the user access control list (ACL) and displays authorization settings for an item under version control.Required PermissionsTo use the permission command, you must have the Manipulate security settings permission set to Allow for the folders being modified, be a member of the Team Foundation Administrators security group, or be a system administrator on the local computer (Windows Administrator security group). For more information, see Team Foundation Server Permissions. </div> <h5>Parameters:</h5> <table class="params"> <thead> <tr> <th>Name</th> <th>Type</th> <th class="last">Description</th> </tr> </thead> <tbody> <tr> <td class="name"><code>itemspec</code></td> <td class="type"> <span class="param-type">Array</span> </td> <td class="description last">File(s) or folder(s) to retrieve. If null/undefined, equals CWD.</td> </tr> <tr> <td class="name"><code>options</code></td> <td class="type"> <span class="param-type">Object</span> </td> <td class="description last">Command options</td> </tr> </tbody> </table> <dl class="details"> <dt class="tag-source">Source:</dt> <dd class="tag-source"><ul class="dummy"><li> <a href="tfs_permission.js.html">tfs/permission.js</a>, <a href="tfs_permission.js.html#line12">line 12</a> </li></ul></dd> </dl> <h4 class="name" id="rename"><span class="type-signature"></span>rename<span class="signature">(itemspec, options)</span><span class="type-signature"></span></h4> <div class="description"> The rename command changes the name or the path of a file or folder. You can use the rename command or the aliases move or ren, to move a file or folder to a new location.Note The results of this command are not reflected in the Team Foundation version control server until you perform a check-in operation. For more information, see Check In Pending Changes.Required PermissionsTo use the rename command, you have the Check out permission set to Allow. For more information, see Team Foundation Server Permissions. </div> <h5>Parameters:</h5> <table class="params"> <thead> <tr> <th>Name</th> <th>Type</th> <th class="last">Description</th> </tr> </thead> <tbody> <tr> <td class="name"><code>itemspec</code></td> <td class="type"> <span class="param-type">Array</span> </td> <td class="description last">File(s) or folder(s) to retrieve. If null/undefined, equals CWD.</td> </tr> <tr> <td class="name"><code>options</code></td> <td class="type"> <span class="param-type">Object</span> </td> <td class="description last">Command options</td> </tr> </tbody> </table> <dl class="details"> <dt class="tag-source">Source:</dt> <dd class="tag-source"><ul class="dummy"><li> <a href="tfs_rename.js.html">tfs/rename.js</a>, <a href="tfs_rename.js.html#line12">line 12</a> </li></ul></dd> </dl> <h4 class="name" id="resolve"><span class="type-signature"></span>resolve<span class="signature">(itemspec, options)</span><span class="type-signature"></span></h4> <div class="description"> Lets you resolve conflicts between changed items in your workspace and the latest or destination versions of items on the server.Required PermissionsTo use the resolve command, you must be either the workspace owner or have the global Administer workspaces permission set to Allow. You must also have the Read and Check out permissions for the items involved in a resolve operation set to Allow. For more information, see Team Foundation Server Permissions. </div> <h5>Parameters:</h5> <table class="params"> <thead> <tr> <th>Name</th> <th>Type</th> <th class="last">Description</th> </tr> </thead> <tbody> <tr> <td class="name"><code>itemspec</code></td> <td class="type"> <span class="param-type">Array</span> </td> <td class="description last">File(s) or folder(s) to retrieve. If null/undefined, equals CWD.</td> </tr> <tr> <td class="name"><code>options</code></td> <td class="type"> <span class="param-type">Object</span> </td> <td class="description last">Command options</td> </tr> </tbody> </table> <dl class="details"> <dt class="tag-source">Source:</dt> <dd class="tag-source"><ul class="dummy"><li> <a href="tfs_resolve.js.html">tfs/resolve.js</a>, <a href="tfs_resolve.js.html#line12">line 12</a> </li></ul></dd> </dl> <h4 class="name" id="rollback"><span class="type-signature"></span>rollback<span class="signature">(itemspec, options)</span><span class="type-signature"></span></h4> <div class="description"> You can use this command to roll back the effects of one or more changesets to one or more version-controlled items. This command does not remove the changesets from an item\'s version history. Instead, this command creates in your workspace a set of pending changes that negate the effects of the changesets that you specify.Required PermissionsTo use this command, you must have the Read, Check Out, and Check In permissions set to Allow. For more information, see Team Foundation Server Permissions. </div> <h5>Parameters:</h5> <table class="params"> <thead> <tr> <th>Name</th> <th>Type</th> <th class="last">Description</th> </tr> </thead> <tbody> <tr> <td class="name"><code>itemspec</code></td> <td class="type"> <span class="param-type">Array</span> </td> <td class="description last">File(s) or folder(s) to retrieve. If null/undefined, equals CWD.</td> </tr> <tr> <td class="name"><code>options</code></td> <td class="type"> <span class="param-type">Object</span> </td> <td class="description last">Command options</td> </tr> </tbody> </table> <dl class="details"> <dt class="tag-source">Source:</dt> <dd class="tag-source"><ul class="dummy"><li> <a href="tfs_rollback.js.html">tfs/rollback.js</a>, <a href="tfs_rollback.js.html#line12">line 12</a> </li></ul></dd> </dl> <h4 class="name" id="setup"><span class="type-signature"></span>setup<span class="signature">()</span><span class="type-signature"> &rarr; {object}</span></h4> <div class="description"> Get TFS settings (after starting setting up if they don't exist yet) </div> <dl class="details"> <dt class="tag-version">Version:</dt> <dd class="tag-version"><ul class="dummy"><li>1.3.0</li></ul></dd> <dt class="tag-source">Source:</dt> <dd class="tag-source"><ul class="dummy"><li> <a href="setup.js.html">setup.js</a>, <a href="setup.js.html#line15">line 15</a> </li></ul></dd> </dl> <h5>Returns:</h5> <div class="param-desc"> Settings </div> <dl> <dt> Type </dt> <dd> <span class="param-type">object</span> </dd> </dl> <h4 class="name" id="shelve"><span class="type-signature"></span>shelve<span class="signature">(itemspec, options)</span><span class="type-signature"></span></h4> <div class="description"> Stores a set of pending changes, together with pending check-in notes, a comment, and a list of associated work items on the server that is running Visual Studio Team Foundation Server without actually checking them into the version control server.Required PermissionsIf you want to use the shelve command to delete a shelveset, you must be a shelveset owner, or your Administer shelved changes permission must be set to Allow. For more information, see Team Foundation Server Permissions. </div> <h5>Parameters:</h5> <table class="params"> <thead> <tr> <th>Name</th> <th>Type</th> <th class="last">Description</th> </tr> </thead> <tbody> <tr> <td class="name"><code>itemspec</code></td> <td class="type"> <span class="param-type">Array</span> </td> <td class="description last">File(s) or folder(s) to retrieve. If null/undefined, equals CWD.</td> </tr> <tr> <td class="name"><code>options</code></td> <td class="type"> <span class="param-type">Object</span> </td> <td class="description last">Command options</td> </tr> </tbody> </table> <dl class="details"> <dt class="tag-source">Source:</dt> <dd class="tag-source"><ul class="dummy"><li> <a href="tfs_shelve.js.html">tfs/shelve.js</a>, <a href="tfs_shelve.js.html#line12">line 12</a> </li></ul></dd> </dl> <h4 class="name" id="shelvesets"><span class="type-signature"></span>shelvesets<span class="signature">(itemspec, options)</span><span class="type-signature"></span></h4> <div class="description"> Displays information about a set of shelved changes.Required PermissionsTo use the shelvesets command, you must the have Read permission and the Check out permission