PoshVsts.dll-Help.xml
|
<?xml version="1.0" encoding="utf-8"?>
<helpItems schema="maml" xmlns="http://msh"> <!-- Cmdlet: Get-VstsBranch --> <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10"> <command:details> <command:name>Get-VstsBranch</command:name> <command:verb>Get</command:verb> <command:noun>VstsBranch</command:noun> <maml:description> <maml:para>Gets branches from Visual Studio Team Services</maml:para> </maml:description> </command:details> <maml:description> <maml:para>The Get-VstsBranch cmdlet retrieves branches from a VSTS project.</maml:para> </maml:description> <command:syntax> <!-- Parameter set: __AllParameterSets --> <command:syntaxItem> <maml:name>Get-VstsBranch</maml:name> <!-- Parameter: AccessToken --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>AccessToken</maml:name> <maml:description> <maml:para>Personal Access Token (PAT) to login to the VSTS-server. If this is not specified, the access token will be read from the current configuration. The access token cannot be shown using Get-VstsConfiguration, but it is possible to update it by Set-VstsConfiguration. The access token is stored in the windows credential store. In case there is no current access token and the AccessToken argument has not been specified, the cmdlet will prompt for a token.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Project --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Project</maml:name> <maml:description> <maml:para>Project name of the Visual Studio Team Services project. If this is not specified, the project will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the project argument has not been specified, the cmdlet will prompt for a project.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Repository --> <command:parameter required="false" globbing="false" pipelineInput="true (ByPropertyName)" position="named" aliases="Name"> <maml:name>Repository</maml:name> <maml:description> <maml:para>Name of the repository. If the connection to VSTS has already been established by running another VSTS-cmdlet, you can cycle through the available repositories via tab-completion.</maml:para> <maml:para>If no repository is specified, but the current path is within a git-repository, that repository will be used. Otherwise there will be an error.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Url --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Url</maml:name> <maml:description> <maml:para>Url of the Visual Studio Team Services instance. If this is not specified, the URL will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the URL argument has not been specified, the cmdlet will prompt for a URL.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> </command:syntaxItem> </command:syntax> <command:parameters> <!-- Parameter: Repository --> <command:parameter required="false" globbing="false" pipelineInput="true (ByPropertyName)" position="named" aliases="Name"> <maml:name>Repository</maml:name> <maml:description> <maml:para>Name of the repository. If the connection to VSTS has already been established by running another VSTS-cmdlet, you can cycle through the available repositories via tab-completion.</maml:para> <maml:para>If no repository is specified, but the current path is within a git-repository, that repository will be used. Otherwise there will be an error.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <command:parameter required="false" globbing="false" pipelineInput="true (ByPropertyName)" position="named" aliases="Name"> <maml:name>Name</maml:name> <maml:description> <maml:para>Name of the repository. If the connection to VSTS has already been established by running another VSTS-cmdlet, you can cycle through the available repositories via tab-completion.</maml:para> <maml:para>If no repository is specified, but the current path is within a git-repository, that repository will be used. Otherwise there will be an error.</maml:para> <maml:para>This is an alias of the Repository parameter.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Url --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Url</maml:name> <maml:description> <maml:para>Url of the Visual Studio Team Services instance. If this is not specified, the URL will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the URL argument has not been specified, the cmdlet will prompt for a URL.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Project --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Project</maml:name> <maml:description> <maml:para>Project name of the Visual Studio Team Services project. If this is not specified, the project will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the project argument has not been specified, the cmdlet will prompt for a project.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: AccessToken --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>AccessToken</maml:name> <maml:description> <maml:para>Personal Access Token (PAT) to login to the VSTS-server. If this is not specified, the access token will be read from the current configuration. The access token cannot be shown using Get-VstsConfiguration, but it is possible to update it by Set-VstsConfiguration. The access token is stored in the windows credential store. In case there is no current access token and the AccessToken argument has not been specified, the cmdlet will prompt for a token.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> </command:parameters> <command:inputTypes> <command:inputType> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> <maml:description> <maml:para>Name of the repository. If the connection to VSTS has already been established by running another VSTS-cmdlet, you can cycle through the available repositories via tab-completion.</maml:para> <maml:para>If no repository is specified, but the current path is within a git-repository, that repository will be used. Otherwise there will be an error.</maml:para> </maml:description> </command:inputType> </command:inputTypes> <command:returnValues /> <command:examples> <command:example> <maml:title>---------- EXAMPLE 1 ----------</maml:title> <dev:code>PS C:\> Get-VstsBranch</dev:code> <dev:remarks> <maml:para>Returns all branches from the current repository in the current project.</maml:para> </dev:remarks> </command:example> <command:example> <maml:title>---------- EXAMPLE 2 ----------</maml:title> <dev:code>PS C:\> Get-VstsBranch -Url https://fabrikam.visualstudio.com -Project xyz</dev:code> <dev:remarks> <maml:para>Returns all branches from the current repository in project xyz in the VSTS-instance at https://fabrikam.visualstudio.com .</maml:para> </dev:remarks> </command:example> <command:example> <maml:title>---------- EXAMPLE 3 ----------</maml:title> <dev:code>PS C:\> Get-VstsBranch -Repository "ProductX"</dev:code> <dev:remarks> <maml:para>Returns all branches from the repository "ProductX" in the current project.</maml:para> </dev:remarks> </command:example> </command:examples> </command:command> <!-- Cmdlet: Get-VstsBuild --> <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10"> <command:details> <command:name>Get-VstsBuild</command:name> <command:verb>Get</command:verb> <command:noun>VstsBuild</command:noun> <maml:description> <maml:para>Gets the builds from Visual Studio Team Services</maml:para> </maml:description> </command:details> <maml:description> <maml:para>The Get-VstsBuild cmdlet gets the builds from a VSTS project.</maml:para> </maml:description> <command:syntax> <!-- Parameter set: __AllParameterSets --> <command:syntaxItem> <maml:name>Get-VstsBuild</maml:name> <!-- Parameter: Id --> <command:parameter required="false" globbing="false" pipelineInput="false" position="0"> <maml:name>Id</maml:name> <maml:description> <maml:para>Id of a build to retrieve.</maml:para> </maml:description> <command:parameterValue required="true">int</command:parameterValue> <dev:type> <maml:name>System.Int32</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>-1</dev:defaultValue> </command:parameter> <!-- Parameter: AccessToken --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>AccessToken</maml:name> <maml:description> <maml:para>Personal Access Token (PAT) to login to the VSTS-server. If this is not specified, the access token will be read from the current configuration. The access token cannot be shown using Get-VstsConfiguration, but it is possible to update it by Set-VstsConfiguration. The access token is stored in the windows credential store. In case there is no current access token and the AccessToken argument has not been specified, the cmdlet will prompt for a token.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Project --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Project</maml:name> <maml:description> <maml:para>Project name of the Visual Studio Team Services project. If this is not specified, the project will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the project argument has not been specified, the cmdlet will prompt for a project.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Url --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Url</maml:name> <maml:description> <maml:para>Url of the Visual Studio Team Services instance. If this is not specified, the URL will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the URL argument has not been specified, the cmdlet will prompt for a URL.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> </command:syntaxItem> </command:syntax> <command:parameters> <!-- Parameter: Id --> <command:parameter required="false" globbing="false" pipelineInput="false" position="0"> <maml:name>Id</maml:name> <maml:description> <maml:para>Id of a build to retrieve.</maml:para> </maml:description> <command:parameterValue required="true">int</command:parameterValue> <dev:type> <maml:name>System.Int32</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>-1</dev:defaultValue> </command:parameter> <!-- Parameter: Url --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Url</maml:name> <maml:description> <maml:para>Url of the Visual Studio Team Services instance. If this is not specified, the URL will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the URL argument has not been specified, the cmdlet will prompt for a URL.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Project --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Project</maml:name> <maml:description> <maml:para>Project name of the Visual Studio Team Services project. If this is not specified, the project will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the project argument has not been specified, the cmdlet will prompt for a project.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: AccessToken --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>AccessToken</maml:name> <maml:description> <maml:para>Personal Access Token (PAT) to login to the VSTS-server. If this is not specified, the access token will be read from the current configuration. The access token cannot be shown using Get-VstsConfiguration, but it is possible to update it by Set-VstsConfiguration. The access token is stored in the windows credential store. In case there is no current access token and the AccessToken argument has not been specified, the cmdlet will prompt for a token.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> </command:parameters> <command:inputTypes /> <command:returnValues /> <command:examples> <command:example> <maml:title>---------- EXAMPLE 1 ----------</maml:title> <dev:code>PS C:\> Get-VstsBuild</dev:code> <dev:remarks> <maml:para>Returns all builds from the current project.</maml:para> </dev:remarks> </command:example> <command:example> <maml:title>---------- EXAMPLE 2 ----------</maml:title> <dev:code>PS C:\> Get-VstsBuild -Url https://fabrikam.visualstudio.com -Project xyz</dev:code> <dev:remarks> <maml:para>Returns all builds from the project xyz in the VSTS-instance at https://fabrikam.visualstudio.com .</maml:para> </dev:remarks> </command:example> <command:example> <maml:title>---------- EXAMPLE 3 ----------</maml:title> <dev:code>PS C:\> Get-VstsBuild 123</dev:code> <dev:remarks> <maml:para>Get build with ID 123 from the current project.</maml:para> </dev:remarks> </command:example> </command:examples> </command:command> <!-- Cmdlet: Start-VstsBuild --> <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10"> <command:details> <command:name>Start-VstsBuild</command:name> <command:verb>Start</command:verb> <command:noun>VstsBuild</command:noun> <maml:description> <maml:para>Starts a build on Visual Studio Team Services</maml:para> </maml:description> </command:details> <maml:description> <maml:para>The Start-VstsBuild cmdlet starts a build on a VSTS project.</maml:para> </maml:description> <command:syntax> <!-- Parameter set: __AllParameterSets --> <command:syntaxItem> <maml:name>Start-VstsBuild</maml:name> <!-- Parameter: BuildDefinition --> <command:parameter required="true" globbing="false" pipelineInput="true (ByPropertyName)" position="1" aliases="Id"> <maml:name>BuildDefinition</maml:name> <maml:description> <maml:para>Id number or build-definition to start a new build for.</maml:para> </maml:description> <command:parameterValue required="true">object</command:parameterValue> <dev:type> <maml:name>System.Object</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: AccessToken --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>AccessToken</maml:name> <maml:description> <maml:para>Personal Access Token (PAT) to login to the VSTS-server. If this is not specified, the access token will be read from the current configuration. The access token cannot be shown using Get-VstsConfiguration, but it is possible to update it by Set-VstsConfiguration. The access token is stored in the windows credential store. In case there is no current access token and the AccessToken argument has not been specified, the cmdlet will prompt for a token.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Project --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Project</maml:name> <maml:description> <maml:para>Project name of the Visual Studio Team Services project. If this is not specified, the project will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the project argument has not been specified, the cmdlet will prompt for a project.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Url --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Url</maml:name> <maml:description> <maml:para>Url of the Visual Studio Team Services instance. If this is not specified, the URL will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the URL argument has not been specified, the cmdlet will prompt for a URL.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> </command:syntaxItem> </command:syntax> <command:parameters> <!-- Parameter: BuildDefinition --> <command:parameter required="true" globbing="false" pipelineInput="true (ByPropertyName)" position="1" aliases="Id"> <maml:name>BuildDefinition</maml:name> <maml:description> <maml:para>Id number or build-definition to start a new build for.</maml:para> </maml:description> <command:parameterValue required="true">object</command:parameterValue> <dev:type> <maml:name>System.Object</maml:name> <maml:uri /> </dev:type> </command:parameter> <command:parameter required="true" globbing="false" pipelineInput="true (ByPropertyName)" position="1" aliases="Id"> <maml:name>Id</maml:name> <maml:description> <maml:para>Id number or build-definition to start a new build for.</maml:para> <maml:para>This is an alias of the BuildDefinition parameter.</maml:para> </maml:description> <command:parameterValue required="true">object</command:parameterValue> <dev:type> <maml:name>System.Object</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Url --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Url</maml:name> <maml:description> <maml:para>Url of the Visual Studio Team Services instance. If this is not specified, the URL will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the URL argument has not been specified, the cmdlet will prompt for a URL.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Project --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Project</maml:name> <maml:description> <maml:para>Project name of the Visual Studio Team Services project. If this is not specified, the project will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the project argument has not been specified, the cmdlet will prompt for a project.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: AccessToken --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>AccessToken</maml:name> <maml:description> <maml:para>Personal Access Token (PAT) to login to the VSTS-server. If this is not specified, the access token will be read from the current configuration. The access token cannot be shown using Get-VstsConfiguration, but it is possible to update it by Set-VstsConfiguration. The access token is stored in the windows credential store. In case there is no current access token and the AccessToken argument has not been specified, the cmdlet will prompt for a token.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> </command:parameters> <command:inputTypes> <command:inputType> <dev:type> <maml:name>System.Object</maml:name> <maml:uri /> </dev:type> <maml:description> <maml:para>Id number or build-definition to start a new build for.</maml:para> </maml:description> </command:inputType> </command:inputTypes> <command:returnValues /> <command:examples> <command:example> <maml:title>---------- EXAMPLE 1 ----------</maml:title> <dev:code>PS C:\> Start-VstsBuild 133</dev:code> <dev:remarks> <maml:para>Starts a new build with the build-definition 133.</maml:para> </dev:remarks> </command:example> <command:example> <maml:title>---------- EXAMPLE 2 ----------</maml:title> <dev:code>PS C:\> Start-VstsBuild 133 -Url https://fabrikam.visualstudio.com -Project xyz</dev:code> <dev:remarks> <maml:para>Starts a new build with the build-definition 133 from the project xyz in the VSTS-instance at https://fabrikam.visualstudio.com .</maml:para> </dev:remarks> </command:example> <command:example> <maml:title>---------- EXAMPLE 3 ----------</maml:title> <dev:code>PS C:\> Start-VstsBuild $buildDefinition</dev:code> <dev:remarks> <maml:para>tarts a new build with the build-definition $buildDefinition.</maml:para> </dev:remarks> </command:example> </command:examples> </command:command> <!-- Cmdlet: Get-VstsBuildDefinition --> <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10"> <command:details> <command:name>Get-VstsBuildDefinition</command:name> <command:verb>Get</command:verb> <command:noun>VstsBuildDefinition</command:noun> <maml:description> <maml:para>Gets the build definitions from Visual Studio Team Services</maml:para> </maml:description> </command:details> <maml:description> <maml:para>The Get-VstsBuildDefinition cmdlet gets the build definitions from a VSTS project.</maml:para> </maml:description> <command:syntax> <!-- Parameter set: __AllParameterSets --> <command:syntaxItem> <maml:name>Get-VstsBuildDefinition</maml:name> <!-- Parameter: AccessToken --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>AccessToken</maml:name> <maml:description> <maml:para>Personal Access Token (PAT) to login to the VSTS-server. If this is not specified, the access token will be read from the current configuration. The access token cannot be shown using Get-VstsConfiguration, but it is possible to update it by Set-VstsConfiguration. The access token is stored in the windows credential store. In case there is no current access token and the AccessToken argument has not been specified, the cmdlet will prompt for a token.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Project --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Project</maml:name> <maml:description> <maml:para>Project name of the Visual Studio Team Services project. If this is not specified, the project will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the project argument has not been specified, the cmdlet will prompt for a project.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Url --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Url</maml:name> <maml:description> <maml:para>Url of the Visual Studio Team Services instance. If this is not specified, the URL will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the URL argument has not been specified, the cmdlet will prompt for a URL.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> </command:syntaxItem> </command:syntax> <command:parameters> <!-- Parameter: Url --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Url</maml:name> <maml:description> <maml:para>Url of the Visual Studio Team Services instance. If this is not specified, the URL will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the URL argument has not been specified, the cmdlet will prompt for a URL.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Project --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Project</maml:name> <maml:description> <maml:para>Project name of the Visual Studio Team Services project. If this is not specified, the project will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the project argument has not been specified, the cmdlet will prompt for a project.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: AccessToken --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>AccessToken</maml:name> <maml:description> <maml:para>Personal Access Token (PAT) to login to the VSTS-server. If this is not specified, the access token will be read from the current configuration. The access token cannot be shown using Get-VstsConfiguration, but it is possible to update it by Set-VstsConfiguration. The access token is stored in the windows credential store. In case there is no current access token and the AccessToken argument has not been specified, the cmdlet will prompt for a token.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> </command:parameters> <command:inputTypes /> <command:returnValues /> <command:examples> <command:example> <maml:title>---------- EXAMPLE 1 ----------</maml:title> <dev:code>PS C:\> Get-VstsBuildDefinition -Url https://fabrikam.visualstudio.com -Project xyz</dev:code> <dev:remarks> <maml:para>Returns all build-definitions from the project xyz in the VSTS-instance at https://fabrikam.visualstudio.com .</maml:para> </dev:remarks> </command:example> <command:example> <maml:title>---------- EXAMPLE 2 ----------</maml:title> <dev:code>PS C:\> Get-VstsBuildDefinition -Project xyz</dev:code> <dev:remarks> <maml:para>Returns all build definitions from the project xyz.</maml:para> </dev:remarks> </command:example> </command:examples> </command:command> <!-- Cmdlet: Get-VstsBuildLog --> <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10"> <command:details> <command:name>Get-VstsBuildLog</command:name> <command:verb>Get</command:verb> <command:noun>VstsBuildLog</command:noun> <maml:description> <maml:para>Gets the build logs from a build in Visual Studio Team Services</maml:para> </maml:description> </command:details> <maml:description> <maml:para>The Get-VstsBuildLog cmdlet gets the build log for a build on VSTS.</maml:para> </maml:description> <command:syntax> <!-- Parameter set: __AllParameterSets --> <command:syntaxItem> <maml:name>Get-VstsBuildLog</maml:name> <!-- Parameter: Build --> <command:parameter required="false" globbing="false" pipelineInput="true (ByPropertyName)" position="1" aliases="Id"> <maml:name>Build</maml:name> <maml:description> <maml:para>Id number or build-instance returned from Get-VstsBuild to get the logs for.</maml:para> <maml:para>Entries will be returned after a log-file has been fully written.</maml:para> </maml:description> <command:parameterValue required="true">object</command:parameterValue> <dev:type> <maml:name>System.Object</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: AccessToken --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>AccessToken</maml:name> <maml:description> <maml:para>Personal Access Token (PAT) to login to the VSTS-server. If this is not specified, the access token will be read from the current configuration. The access token cannot be shown using Get-VstsConfiguration, but it is possible to update it by Set-VstsConfiguration. The access token is stored in the windows credential store. In case there is no current access token and the AccessToken argument has not been specified, the cmdlet will prompt for a token.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Pretty --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Pretty</maml:name> <maml:description> <maml:para>Returns the log entries as text formatted for better readability.</maml:para> <maml:para>Use this switch if you want to read the log on the screen. If you want to process or analyze log entries, do not specify the switch so that log entries will be returned as objects with properties instead of text.</maml:para> </maml:description> <command:parameterValue required="true">SwitchParameter</command:parameterValue> <dev:type> <maml:name>System.Management.Automation.SwitchParameter</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>False</dev:defaultValue> </command:parameter> <!-- Parameter: Project --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Project</maml:name> <maml:description> <maml:para>Project name of the Visual Studio Team Services project. If this is not specified, the project will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the project argument has not been specified, the cmdlet will prompt for a project.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Url --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Url</maml:name> <maml:description> <maml:para>Url of the Visual Studio Team Services instance. If this is not specified, the URL will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the URL argument has not been specified, the cmdlet will prompt for a URL.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> </command:syntaxItem> </command:syntax> <command:parameters> <!-- Parameter: Build --> <command:parameter required="false" globbing="false" pipelineInput="true (ByPropertyName)" position="1" aliases="Id"> <maml:name>Build</maml:name> <maml:description> <maml:para>Id number or build-instance returned from Get-VstsBuild to get the logs for.</maml:para> <maml:para>Entries will be returned after a log-file has been fully written.</maml:para> </maml:description> <command:parameterValue required="true">object</command:parameterValue> <dev:type> <maml:name>System.Object</maml:name> <maml:uri /> </dev:type> </command:parameter> <command:parameter required="false" globbing="false" pipelineInput="true (ByPropertyName)" position="1" aliases="Id"> <maml:name>Id</maml:name> <maml:description> <maml:para>Id number or build-instance returned from Get-VstsBuild to get the logs for.</maml:para> <maml:para>Entries will be returned after a log-file has been fully written.</maml:para> <maml:para>This is an alias of the Build parameter.</maml:para> </maml:description> <command:parameterValue required="true">object</command:parameterValue> <dev:type> <maml:name>System.Object</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Pretty --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Pretty</maml:name> <maml:description> <maml:para>Returns the log entries as text formatted for better readability.</maml:para> <maml:para>Use this switch if you want to read the log on the screen. If you want to process or analyze log entries, do not specify the switch so that log entries will be returned as objects with properties instead of text.</maml:para> </maml:description> <command:parameterValue required="true">SwitchParameter</command:parameterValue> <dev:type> <maml:name>System.Management.Automation.SwitchParameter</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>False</dev:defaultValue> </command:parameter> <!-- Parameter: Url --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Url</maml:name> <maml:description> <maml:para>Url of the Visual Studio Team Services instance. If this is not specified, the URL will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the URL argument has not been specified, the cmdlet will prompt for a URL.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Project --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Project</maml:name> <maml:description> <maml:para>Project name of the Visual Studio Team Services project. If this is not specified, the project will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the project argument has not been specified, the cmdlet will prompt for a project.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: AccessToken --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>AccessToken</maml:name> <maml:description> <maml:para>Personal Access Token (PAT) to login to the VSTS-server. If this is not specified, the access token will be read from the current configuration. The access token cannot be shown using Get-VstsConfiguration, but it is possible to update it by Set-VstsConfiguration. The access token is stored in the windows credential store. In case there is no current access token and the AccessToken argument has not been specified, the cmdlet will prompt for a token.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> </command:parameters> <command:inputTypes> <command:inputType> <dev:type> <maml:name>System.Object</maml:name> <maml:uri /> </dev:type> <maml:description> <maml:para>Id number or build-instance returned from Get-VstsBuild to get the logs for.</maml:para> <maml:para>Entries will be returned after a log-file has been fully written.</maml:para> </maml:description> </command:inputType> </command:inputTypes> <command:returnValues /> <command:examples> <command:example> <maml:title>---------- EXAMPLE 1 ----------</maml:title> <dev:code>PS C:\> Get-VstsBuildLog 133</dev:code> <dev:remarks> <maml:para>Returns all log entries for the build with ID 133.</maml:para> </dev:remarks> </command:example> <command:example> <maml:title>---------- EXAMPLE 2 ----------</maml:title> <dev:code>PS C:\> Get-VstsBuildLog 133 -Url https://fabrikam.visualstudio.com -Project xyz</dev:code> <dev:remarks> <maml:para>Returns all log entries for the build with ID 133 from the project xyz in the VSTS-instance at https://fabrikam.visualstudio.com .</maml:para> </dev:remarks> </command:example> <command:example> <maml:title>---------- EXAMPLE 3 ----------</maml:title> <dev:code>PS C:\> Get-VstsBuildLog -Id 323 -Pretty</dev:code> <dev:remarks> <maml:para>Returns all log entries for the build with ID 323 formatted for readability.</maml:para> </dev:remarks> </command:example> <command:example> <maml:title>---------- EXAMPLE 4 ----------</maml:title> <dev:code>PS C:\> Get-VstsBuildLog -Build $build</dev:code> <dev:remarks> <maml:para>Returns all log entries for the build in $build.</maml:para> </dev:remarks> </command:example> <command:example> <maml:title>---------- EXAMPLE 5 ----------</maml:title> <dev:code>PS C:\> $build | Get-VstsBuildLog</dev:code> <dev:remarks> <maml:para>Returns all log entries for the build in $build.</maml:para> </dev:remarks> </command:example> </command:examples> </command:command> <!-- Cmdlet: Get-VstsConfiguration --> <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10"> <command:details> <command:name>Get-VstsConfiguration</command:name> <command:verb>Get</command:verb> <command:noun>VstsConfiguration</command:noun> </command:details> <command:syntax> <!-- Parameter set: __AllParameterSets --> <command:syntaxItem> <maml:name>Get-VstsConfiguration</maml:name> </command:syntaxItem> </command:syntax> <command:parameters /> <command:inputTypes /> <command:returnValues /> </command:command> <!-- Cmdlet: Set-VstsConfiguration --> <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10"> <command:details> <command:name>Set-VstsConfiguration</command:name> <command:verb>Set</command:verb> <command:noun>VstsConfiguration</command:noun> </command:details> <command:syntax> <!-- Parameter set: __AllParameterSets --> <command:syntaxItem> <maml:name>Set-VstsConfiguration</maml:name> <!-- Parameter: AccessToken --> <command:parameter required="false" globbing="false" pipelineInput="true (ByPropertyName)" position="named"> <maml:name>AccessToken</maml:name> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Project --> <command:parameter required="false" globbing="false" pipelineInput="true (ByPropertyName)" position="named"> <maml:name>Project</maml:name> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Url --> <command:parameter required="false" globbing="false" pipelineInput="true (ByPropertyName)" position="named"> <maml:name>Url</maml:name> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> </command:syntaxItem> </command:syntax> <command:parameters> <!-- Parameter: Url --> <command:parameter required="false" globbing="false" pipelineInput="true (ByPropertyName)" position="named"> <maml:name>Url</maml:name> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Project --> <command:parameter required="false" globbing="false" pipelineInput="true (ByPropertyName)" position="named"> <maml:name>Project</maml:name> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: AccessToken --> <command:parameter required="false" globbing="false" pipelineInput="true (ByPropertyName)" position="named"> <maml:name>AccessToken</maml:name> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> </command:parameters> <command:inputTypes> <command:inputType> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:inputType> <command:inputType> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:inputType> <command:inputType> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:inputType> </command:inputTypes> <command:returnValues /> </command:command> <!-- Cmdlet: Get-VstsIteration --> <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10"> <command:details> <command:name>Get-VstsIteration</command:name> <command:verb>Get</command:verb> <command:noun>VstsIteration</command:noun> </command:details> <command:syntax> <!-- Parameter set: __AllParameterSets --> <command:syntaxItem> <maml:name>Get-VstsIteration</maml:name> <!-- Parameter: AccessToken --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>AccessToken</maml:name> <maml:description> <maml:para>Personal Access Token (PAT) to login to the VSTS-server. If this is not specified, the access token will be read from the current configuration. The access token cannot be shown using Get-VstsConfiguration, but it is possible to update it by Set-VstsConfiguration. The access token is stored in the windows credential store. In case there is no current access token and the AccessToken argument has not been specified, the cmdlet will prompt for a token.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Project --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Project</maml:name> <maml:description> <maml:para>Project name of the Visual Studio Team Services project. If this is not specified, the project will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the project argument has not been specified, the cmdlet will prompt for a project.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Url --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Url</maml:name> <maml:description> <maml:para>Url of the Visual Studio Team Services instance. If this is not specified, the URL will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the URL argument has not been specified, the cmdlet will prompt for a URL.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> </command:syntaxItem> </command:syntax> <command:parameters> <!-- Parameter: Url --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Url</maml:name> <maml:description> <maml:para>Url of the Visual Studio Team Services instance. If this is not specified, the URL will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the URL argument has not been specified, the cmdlet will prompt for a URL.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Project --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Project</maml:name> <maml:description> <maml:para>Project name of the Visual Studio Team Services project. If this is not specified, the project will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the project argument has not been specified, the cmdlet will prompt for a project.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: AccessToken --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>AccessToken</maml:name> <maml:description> <maml:para>Personal Access Token (PAT) to login to the VSTS-server. If this is not specified, the access token will be read from the current configuration. The access token cannot be shown using Get-VstsConfiguration, but it is possible to update it by Set-VstsConfiguration. The access token is stored in the windows credential store. In case there is no current access token and the AccessToken argument has not been specified, the cmdlet will prompt for a token.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> </command:parameters> <command:inputTypes /> <command:returnValues /> </command:command> <!-- Cmdlet: Get-VstsPullRequest --> <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10"> <command:details> <command:name>Get-VstsPullRequest</command:name> <command:verb>Get</command:verb> <command:noun>VstsPullRequest</command:noun> <maml:description> <maml:para>Gets the pull-requests from Visual Studio Team Services</maml:para> </maml:description> </command:details> <maml:description> <maml:para>The Get-VstsPullRequest cmdlet gets the pull-requests from a VSTS project.</maml:para> </maml:description> <command:syntax> <!-- Parameter set: __AllParameterSets --> <command:syntaxItem> <maml:name>Get-VstsPullRequest</maml:name> <!-- Parameter: AccessToken --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>AccessToken</maml:name> <maml:description> <maml:para>Personal Access Token (PAT) to login to the VSTS-server. If this is not specified, the access token will be read from the current configuration. The access token cannot be shown using Get-VstsConfiguration, but it is possible to update it by Set-VstsConfiguration. The access token is stored in the windows credential store. In case there is no current access token and the AccessToken argument has not been specified, the cmdlet will prompt for a token.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Project --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Project</maml:name> <maml:description> <maml:para>Project name of the Visual Studio Team Services project. If this is not specified, the project will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the project argument has not been specified, the cmdlet will prompt for a project.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Url --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Url</maml:name> <maml:description> <maml:para>Url of the Visual Studio Team Services instance. If this is not specified, the URL will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the URL argument has not been specified, the cmdlet will prompt for a URL.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> </command:syntaxItem> </command:syntax> <command:parameters> <!-- Parameter: Url --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Url</maml:name> <maml:description> <maml:para>Url of the Visual Studio Team Services instance. If this is not specified, the URL will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the URL argument has not been specified, the cmdlet will prompt for a URL.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Project --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Project</maml:name> <maml:description> <maml:para>Project name of the Visual Studio Team Services project. If this is not specified, the project will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the project argument has not been specified, the cmdlet will prompt for a project.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: AccessToken --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>AccessToken</maml:name> <maml:description> <maml:para>Personal Access Token (PAT) to login to the VSTS-server. If this is not specified, the access token will be read from the current configuration. The access token cannot be shown using Get-VstsConfiguration, but it is possible to update it by Set-VstsConfiguration. The access token is stored in the windows credential store. In case there is no current access token and the AccessToken argument has not been specified, the cmdlet will prompt for a token.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> </command:parameters> <command:inputTypes /> <command:returnValues /> <command:examples> <command:example> <maml:title>---------- EXAMPLE 1 ----------</maml:title> <dev:code>PS C:\> Get-VstsPullRequest</dev:code> <dev:remarks> <maml:para>Returns all pull-requests from the current project.</maml:para> </dev:remarks> </command:example> <command:example> <maml:title>---------- EXAMPLE 2 ----------</maml:title> <dev:code>PS C:\> Get-VstsPullRequest -Url https://fabrikam.visualstudio.com -Project xyz</dev:code> <dev:remarks> <maml:para>Returns all pull-requests from the project xyz in the VSTS-instance at https://fabrikam.visualstudio.com .</maml:para> </dev:remarks> </command:example> </command:examples> </command:command> <!-- Cmdlet: New-VstsPullRequest --> <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10"> <command:details> <command:name>New-VstsPullRequest</command:name> <command:verb>New</command:verb> <command:noun>VstsPullRequest</command:noun> <maml:description> <maml:para>Creates a new pull-request on Visual Studio Team Services</maml:para> </maml:description> </command:details> <maml:description> <maml:para>The New-VstsPullRequest cmdlet creates a new pull-request on a VSTS project.</maml:para> </maml:description> <command:syntax> <!-- Parameter set: __AllParameterSets --> <command:syntaxItem> <maml:name>New-VstsPullRequest</maml:name> <!-- Parameter: Title --> <command:parameter required="true" globbing="false" pipelineInput="false" position="0"> <maml:name>Title</maml:name> <maml:description> <maml:para>Title of the pull request.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: TargetBranch --> <command:parameter required="true" globbing="false" pipelineInput="false" position="1"> <maml:name>TargetBranch</maml:name> <maml:description> <maml:para>Name of the target branch. If the connection to VSTS has already been established by running another VSTS-cmdlet, you can cycle through the available branches via tab-completion.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: AccessToken --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>AccessToken</maml:name> <maml:description> <maml:para>Personal Access Token (PAT) to login to the VSTS-server. If this is not specified, the access token will be read from the current configuration. The access token cannot be shown using Get-VstsConfiguration, but it is possible to update it by Set-VstsConfiguration. The access token is stored in the windows credential store. In case there is no current access token and the AccessToken argument has not been specified, the cmdlet will prompt for a token.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Project --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Project</maml:name> <maml:description> <maml:para>Project name of the Visual Studio Team Services project. If this is not specified, the project will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the project argument has not been specified, the cmdlet will prompt for a project.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Repository --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Repository</maml:name> <maml:description> <maml:para>Name of the repository. If the connection to VSTS has already been established by running another VSTS-cmdlet, you can cycle through the available repositories via tab-completion.</maml:para> <maml:para>If no repository is specified, but the current path is within a git-repository, that repository will be used. Otherwise there will be an error.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: SourceBranch --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>SourceBranch</maml:name> <maml:description> <maml:para>Name of the source branch. If the connection to VSTS has already been established by running another VSTS-cmdlet, you can cycle through the available branches via tab-completion.</maml:para> <maml:para>If no source branch is specified, but the current path is within a git-repository, the currently checked out branch will be assumed to be the source. Otherwise there will be an error.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Url --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Url</maml:name> <maml:description> <maml:para>Url of the Visual Studio Team Services instance. If this is not specified, the URL will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the URL argument has not been specified, the cmdlet will prompt for a URL.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> </command:syntaxItem> </command:syntax> <command:parameters> <!-- Parameter: Title --> <command:parameter required="true" globbing="false" pipelineInput="false" position="0"> <maml:name>Title</maml:name> <maml:description> <maml:para>Title of the pull request.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: TargetBranch --> <command:parameter required="true" globbing="false" pipelineInput="false" position="1"> <maml:name>TargetBranch</maml:name> <maml:description> <maml:para>Name of the target branch. If the connection to VSTS has already been established by running another VSTS-cmdlet, you can cycle through the available branches via tab-completion.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Repository --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Repository</maml:name> <maml:description> <maml:para>Name of the repository. If the connection to VSTS has already been established by running another VSTS-cmdlet, you can cycle through the available repositories via tab-completion.</maml:para> <maml:para>If no repository is specified, but the current path is within a git-repository, that repository will be used. Otherwise there will be an error.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: SourceBranch --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>SourceBranch</maml:name> <maml:description> <maml:para>Name of the source branch. If the connection to VSTS has already been established by running another VSTS-cmdlet, you can cycle through the available branches via tab-completion.</maml:para> <maml:para>If no source branch is specified, but the current path is within a git-repository, the currently checked out branch will be assumed to be the source. Otherwise there will be an error.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Url --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Url</maml:name> <maml:description> <maml:para>Url of the Visual Studio Team Services instance. If this is not specified, the URL will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the URL argument has not been specified, the cmdlet will prompt for a URL.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Project --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Project</maml:name> <maml:description> <maml:para>Project name of the Visual Studio Team Services project. If this is not specified, the project will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the project argument has not been specified, the cmdlet will prompt for a project.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: AccessToken --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>AccessToken</maml:name> <maml:description> <maml:para>Personal Access Token (PAT) to login to the VSTS-server. If this is not specified, the access token will be read from the current configuration. The access token cannot be shown using Get-VstsConfiguration, but it is possible to update it by Set-VstsConfiguration. The access token is stored in the windows credential store. In case there is no current access token and the AccessToken argument has not been specified, the cmdlet will prompt for a token.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> </command:parameters> <command:inputTypes /> <command:returnValues /> <command:examples> <command:example> <maml:title>---------- EXAMPLE 1 ----------</maml:title> <dev:code>PS C:\> New-VstsPullRequest "Made some minor adjustments" "master"</dev:code> <dev:remarks> <maml:para>Creates a new pull-request with the title "Made some minor adjustments". It will request to pull the changes from the current branch into the branch "master".</maml:para> </dev:remarks> </command:example> <command:example> <maml:title>---------- EXAMPLE 2 ----------</maml:title> <dev:code>PS C:\> New-VstsPullRequest -Title "Made some minor adjustments" -Repository "ProductX" -SourceBranch "MyFeature" -TargetBranch "master"</dev:code> <dev:remarks> <maml:para>Creates a new pull-request with the title "Made some minor adjustments". It will request to pull the changes from the branch "MyFeature" in repository "ProductX" into the branch "master" in repository "ProductX".</maml:para> </dev:remarks> </command:example> <command:example> <maml:title>---------- EXAMPLE 3 ----------</maml:title> <dev:code>PS C:\> New-VstsPullRequest Made some minor adjustments" "master" -Url https://fabrikam.visualstudio.com -Project xyz</dev:code> <dev:remarks> <maml:para>Creates a new pull-request with the title "Made some minor adjustments". It will request to pull the changes from the current branch into the branch "master" of the project xyz in the VSTS-instance at https://fabrikam.visualstudio.com .</maml:para> </dev:remarks> </command:example> </command:examples> </command:command> <!-- Cmdlet: Update-VstsPullRequest --> <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10"> <command:details> <command:name>Update-VstsPullRequest</command:name> <command:verb>Update</command:verb> <command:noun>VstsPullRequest</command:noun> <maml:description> <maml:para>Updates a pull-request in Visual Studio Team Services</maml:para> </maml:description> </command:details> <maml:description> <maml:para>The Update-VstsPullRequest cmdlet gets updates a pull-request on a VSTS project.</maml:para> </maml:description> <command:syntax> <!-- Parameter set: __AllParameterSets --> <command:syntaxItem> <maml:name>Update-VstsPullRequest</maml:name> <!-- Parameter: PullRequestId --> <command:parameter required="true" globbing="false" pipelineInput="true (ByPropertyName)" position="0"> <maml:name>PullRequestId</maml:name> <maml:description> <maml:para>Id number or pull-request-instance returned from Get-VstsPullRequest to update.</maml:para> </maml:description> <command:parameterValue required="true">int</command:parameterValue> <dev:type> <maml:name>System.Int32</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>0</dev:defaultValue> </command:parameter> <!-- Parameter: AccessToken --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>AccessToken</maml:name> <maml:description> <maml:para>Personal Access Token (PAT) to login to the VSTS-server. If this is not specified, the access token will be read from the current configuration. The access token cannot be shown using Get-VstsConfiguration, but it is possible to update it by Set-VstsConfiguration. The access token is stored in the windows credential store. In case there is no current access token and the AccessToken argument has not been specified, the cmdlet will prompt for a token.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Description --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Description</maml:name> <maml:description> <maml:para>New description of the pull-request.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Project --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Project</maml:name> <maml:description> <maml:para>Project name of the Visual Studio Team Services project. If this is not specified, the project will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the project argument has not been specified, the cmdlet will prompt for a project.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Repository --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Repository</maml:name> <maml:description> <maml:para>Name of the repository. If the connection to VSTS has already been established by running another VSTS-cmdlet, you can cycle through the available repositories via tab-completion.</maml:para> <maml:para>If no repository is specified, but the current path is within a git-repository, that repository will be used. Otherwise there will be an error.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Title --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Title</maml:name> <maml:description> <maml:para>New title of the pull-request.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Url --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Url</maml:name> <maml:description> <maml:para>Url of the Visual Studio Team Services instance. If this is not specified, the URL will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the URL argument has not been specified, the cmdlet will prompt for a URL.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> </command:syntaxItem> </command:syntax> <command:parameters> <!-- Parameter: PullRequestId --> <command:parameter required="true" globbing="false" pipelineInput="true (ByPropertyName)" position="0"> <maml:name>PullRequestId</maml:name> <maml:description> <maml:para>Id number or pull-request-instance returned from Get-VstsPullRequest to update.</maml:para> </maml:description> <command:parameterValue required="true">int</command:parameterValue> <dev:type> <maml:name>System.Int32</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>0</dev:defaultValue> </command:parameter> <!-- Parameter: Repository --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Repository</maml:name> <maml:description> <maml:para>Name of the repository. If the connection to VSTS has already been established by running another VSTS-cmdlet, you can cycle through the available repositories via tab-completion.</maml:para> <maml:para>If no repository is specified, but the current path is within a git-repository, that repository will be used. Otherwise there will be an error.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Title --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Title</maml:name> <maml:description> <maml:para>New title of the pull-request.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Description --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Description</maml:name> <maml:description> <maml:para>New description of the pull-request.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Url --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Url</maml:name> <maml:description> <maml:para>Url of the Visual Studio Team Services instance. If this is not specified, the URL will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the URL argument has not been specified, the cmdlet will prompt for a URL.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Project --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Project</maml:name> <maml:description> <maml:para>Project name of the Visual Studio Team Services project. If this is not specified, the project will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the project argument has not been specified, the cmdlet will prompt for a project.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: AccessToken --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>AccessToken</maml:name> <maml:description> <maml:para>Personal Access Token (PAT) to login to the VSTS-server. If this is not specified, the access token will be read from the current configuration. The access token cannot be shown using Get-VstsConfiguration, but it is possible to update it by Set-VstsConfiguration. The access token is stored in the windows credential store. In case there is no current access token and the AccessToken argument has not been specified, the cmdlet will prompt for a token.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> </command:parameters> <command:inputTypes> <command:inputType> <dev:type> <maml:name>System.Int32</maml:name> <maml:uri /> </dev:type> <maml:description> <maml:para>Id number or pull-request-instance returned from Get-VstsPullRequest to update.</maml:para> </maml:description> </command:inputType> </command:inputTypes> <command:returnValues /> <command:examples> <command:example> <maml:title>---------- EXAMPLE 1 ----------</maml:title> <dev:code>PS C:\> Update-VstsPullRequest 314 -Title "This is a new title"</dev:code> <dev:remarks> <maml:para>Updates the title of pull-request with Id 314 in the current repository to be "This is a new title"</maml:para> </dev:remarks> </command:example> <command:example> <maml:title>---------- EXAMPLE 2 ----------</maml:title> <dev:code>PS C:\> Update-VstsPullRequest $pullRequest -Repository "ProductX" -Description "This is a new description"</dev:code> <dev:remarks> <maml:para>Updates the description of the pull-request $pullRequest in the repository "ProductX" to be "This is a new description"</maml:para> </dev:remarks> </command:example> </command:examples> </command:command> <!-- Cmdlet: Add-VstsRelation --> <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10"> <command:details> <command:name>Add-VstsRelation</command:name> <command:verb>Add</command:verb> <command:noun>VstsRelation</command:noun> </command:details> <command:syntax> <!-- Parameter set: __AllParameterSets --> <command:syntaxItem> <maml:name>Add-VstsRelation</maml:name> <!-- Parameter: Item --> <command:parameter required="true" globbing="false" pipelineInput="true (ByValue)" position="1"> <maml:name>Item</maml:name> <command:parameterValue required="true">VstsWorkItem</command:parameterValue> <dev:type> <maml:name>PoshVsts.VstsWorkItem</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Type --> <command:parameter required="true" globbing="false" pipelineInput="false" position="2"> <maml:name>Type</maml:name> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: RelatedItem --> <command:parameter required="true" globbing="false" pipelineInput="false" position="3" aliases="RelatedItemId"> <maml:name>RelatedItem</maml:name> <command:parameterValue required="true">object</command:parameterValue> <dev:type> <maml:name>System.Object</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: AccessToken --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>AccessToken</maml:name> <maml:description> <maml:para>Personal Access Token (PAT) to login to the VSTS-server. If this is not specified, the access token will be read from the current configuration. The access token cannot be shown using Get-VstsConfiguration, but it is possible to update it by Set-VstsConfiguration. The access token is stored in the windows credential store. In case there is no current access token and the AccessToken argument has not been specified, the cmdlet will prompt for a token.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Project --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Project</maml:name> <maml:description> <maml:para>Project name of the Visual Studio Team Services project. If this is not specified, the project will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the project argument has not been specified, the cmdlet will prompt for a project.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Repository --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named" aliases="Name"> <maml:name>Repository</maml:name> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Url --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Url</maml:name> <maml:description> <maml:para>Url of the Visual Studio Team Services instance. If this is not specified, the URL will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the URL argument has not been specified, the cmdlet will prompt for a URL.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> </command:syntaxItem> </command:syntax> <command:parameters> <!-- Parameter: Item --> <command:parameter required="true" globbing="false" pipelineInput="true (ByValue)" position="1"> <maml:name>Item</maml:name> <command:parameterValue required="true">VstsWorkItem</command:parameterValue> <dev:type> <maml:name>PoshVsts.VstsWorkItem</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Type --> <command:parameter required="true" globbing="false" pipelineInput="false" position="2"> <maml:name>Type</maml:name> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: RelatedItem --> <command:parameter required="true" globbing="false" pipelineInput="false" position="3" aliases="RelatedItemId"> <maml:name>RelatedItem</maml:name> <command:parameterValue required="true">object</command:parameterValue> <dev:type> <maml:name>System.Object</maml:name> <maml:uri /> </dev:type> </command:parameter> <command:parameter required="true" globbing="false" pipelineInput="false" position="3" aliases="RelatedItemId"> <maml:name>RelatedItemId</maml:name> <command:parameterValue required="true">object</command:parameterValue> <dev:type> <maml:name>System.Object</maml:name> <maml:uri /> </dev:type> <maml:description> <maml:para>This is an alias of the RelatedItem parameter.</maml:para> </maml:description> </command:parameter> <!-- Parameter: Repository --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named" aliases="Name"> <maml:name>Repository</maml:name> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <command:parameter required="false" globbing="false" pipelineInput="false" position="named" aliases="Name"> <maml:name>Name</maml:name> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> <maml:description> <maml:para>This is an alias of the Repository parameter.</maml:para> </maml:description> </command:parameter> <!-- Parameter: Url --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Url</maml:name> <maml:description> <maml:para>Url of the Visual Studio Team Services instance. If this is not specified, the URL will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the URL argument has not been specified, the cmdlet will prompt for a URL.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Project --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Project</maml:name> <maml:description> <maml:para>Project name of the Visual Studio Team Services project. If this is not specified, the project will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the project argument has not been specified, the cmdlet will prompt for a project.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: AccessToken --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>AccessToken</maml:name> <maml:description> <maml:para>Personal Access Token (PAT) to login to the VSTS-server. If this is not specified, the access token will be read from the current configuration. The access token cannot be shown using Get-VstsConfiguration, but it is possible to update it by Set-VstsConfiguration. The access token is stored in the windows credential store. In case there is no current access token and the AccessToken argument has not been specified, the cmdlet will prompt for a token.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> </command:parameters> <command:inputTypes> <command:inputType> <dev:type> <maml:name>PoshVsts.VstsWorkItem</maml:name> <maml:uri /> </dev:type> </command:inputType> </command:inputTypes> <command:returnValues /> </command:command> <!-- Cmdlet: Remove-VstsRelation --> <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10"> <command:details> <command:name>Remove-VstsRelation</command:name> <command:verb>Remove</command:verb> <command:noun>VstsRelation</command:noun> </command:details> <command:syntax> <!-- Parameter set: __AllParameterSets --> <command:syntaxItem> <maml:name>Remove-VstsRelation</maml:name> <!-- Parameter: Item --> <command:parameter required="true" globbing="false" pipelineInput="true (ByValue)" position="1"> <maml:name>Item</maml:name> <command:parameterValue required="true">VstsWorkItem</command:parameterValue> <dev:type> <maml:name>PoshVsts.VstsWorkItem</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Relation --> <command:parameter required="false" globbing="false" pipelineInput="false" position="2"> <maml:name>Relation</maml:name> <command:parameterValue required="true">object</command:parameterValue> <dev:type> <maml:name>System.Object</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: AccessToken --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>AccessToken</maml:name> <maml:description> <maml:para>Personal Access Token (PAT) to login to the VSTS-server. If this is not specified, the access token will be read from the current configuration. The access token cannot be shown using Get-VstsConfiguration, but it is possible to update it by Set-VstsConfiguration. The access token is stored in the windows credential store. In case there is no current access token and the AccessToken argument has not been specified, the cmdlet will prompt for a token.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Project --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Project</maml:name> <maml:description> <maml:para>Project name of the Visual Studio Team Services project. If this is not specified, the project will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the project argument has not been specified, the cmdlet will prompt for a project.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Url --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Url</maml:name> <maml:description> <maml:para>Url of the Visual Studio Team Services instance. If this is not specified, the URL will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the URL argument has not been specified, the cmdlet will prompt for a URL.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> </command:syntaxItem> </command:syntax> <command:parameters> <!-- Parameter: Item --> <command:parameter required="true" globbing="false" pipelineInput="true (ByValue)" position="1"> <maml:name>Item</maml:name> <command:parameterValue required="true">VstsWorkItem</command:parameterValue> <dev:type> <maml:name>PoshVsts.VstsWorkItem</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Relation --> <command:parameter required="false" globbing="false" pipelineInput="false" position="2"> <maml:name>Relation</maml:name> <command:parameterValue required="true">object</command:parameterValue> <dev:type> <maml:name>System.Object</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Url --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Url</maml:name> <maml:description> <maml:para>Url of the Visual Studio Team Services instance. If this is not specified, the URL will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the URL argument has not been specified, the cmdlet will prompt for a URL.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Project --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Project</maml:name> <maml:description> <maml:para>Project name of the Visual Studio Team Services project. If this is not specified, the project will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the project argument has not been specified, the cmdlet will prompt for a project.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: AccessToken --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>AccessToken</maml:name> <maml:description> <maml:para>Personal Access Token (PAT) to login to the VSTS-server. If this is not specified, the access token will be read from the current configuration. The access token cannot be shown using Get-VstsConfiguration, but it is possible to update it by Set-VstsConfiguration. The access token is stored in the windows credential store. In case there is no current access token and the AccessToken argument has not been specified, the cmdlet will prompt for a token.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> </command:parameters> <command:inputTypes> <command:inputType> <dev:type> <maml:name>PoshVsts.VstsWorkItem</maml:name> <maml:uri /> </dev:type> </command:inputType> </command:inputTypes> <command:returnValues /> </command:command> <!-- Cmdlet: Get-VstsRelease --> <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10"> <command:details> <command:name>Get-VstsRelease</command:name> <command:verb>Get</command:verb> <command:noun>VstsRelease</command:noun> <maml:description> <maml:para>Gets the releases from Visual Studio Team Services</maml:para> </maml:description> </command:details> <maml:description> <maml:para>The Get-VstsRelease cmdlet gets the releases from a VSTS project.</maml:para> </maml:description> <command:syntax> <!-- Parameter set: __AllParameterSets --> <command:syntaxItem> <maml:name>Get-VstsRelease</maml:name> <!-- Parameter: Id --> <command:parameter required="false" globbing="false" pipelineInput="false" position="0"> <maml:name>Id</maml:name> <maml:description> <maml:para>Id of a release to retrieve.</maml:para> </maml:description> <command:parameterValue required="true">int</command:parameterValue> <dev:type> <maml:name>System.Int32</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>-1</dev:defaultValue> </command:parameter> <!-- Parameter: AccessToken --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>AccessToken</maml:name> <maml:description> <maml:para>Personal Access Token (PAT) to login to the VSTS-server. If this is not specified, the access token will be read from the current configuration. The access token cannot be shown using Get-VstsConfiguration, but it is possible to update it by Set-VstsConfiguration. The access token is stored in the windows credential store. In case there is no current access token and the AccessToken argument has not been specified, the cmdlet will prompt for a token.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Project --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Project</maml:name> <maml:description> <maml:para>Project name of the Visual Studio Team Services project. If this is not specified, the project will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the project argument has not been specified, the cmdlet will prompt for a project.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Url --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Url</maml:name> <maml:description> <maml:para>Url of the Visual Studio Team Services instance. If this is not specified, the URL will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the URL argument has not been specified, the cmdlet will prompt for a URL.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> </command:syntaxItem> </command:syntax> <command:parameters> <!-- Parameter: Id --> <command:parameter required="false" globbing="false" pipelineInput="false" position="0"> <maml:name>Id</maml:name> <maml:description> <maml:para>Id of a release to retrieve.</maml:para> </maml:description> <command:parameterValue required="true">int</command:parameterValue> <dev:type> <maml:name>System.Int32</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>-1</dev:defaultValue> </command:parameter> <!-- Parameter: Url --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Url</maml:name> <maml:description> <maml:para>Url of the Visual Studio Team Services instance. If this is not specified, the URL will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the URL argument has not been specified, the cmdlet will prompt for a URL.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Project --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Project</maml:name> <maml:description> <maml:para>Project name of the Visual Studio Team Services project. If this is not specified, the project will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the project argument has not been specified, the cmdlet will prompt for a project.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: AccessToken --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>AccessToken</maml:name> <maml:description> <maml:para>Personal Access Token (PAT) to login to the VSTS-server. If this is not specified, the access token will be read from the current configuration. The access token cannot be shown using Get-VstsConfiguration, but it is possible to update it by Set-VstsConfiguration. The access token is stored in the windows credential store. In case there is no current access token and the AccessToken argument has not been specified, the cmdlet will prompt for a token.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> </command:parameters> <command:inputTypes /> <command:returnValues /> <command:examples> <command:example> <maml:title>---------- EXAMPLE 1 ----------</maml:title> <dev:code>PS C:\> Get-VstsRelease</dev:code> <dev:remarks> <maml:para>Returns all releases from the current project.</maml:para> </dev:remarks> </command:example> <command:example> <maml:title>---------- EXAMPLE 2 ----------</maml:title> <dev:code>PS C:\> Get-VstsRelease -Url https://fabrikam.visualstudio.com -Project xyz</dev:code> <dev:remarks> <maml:para>Returns all releases from the project xyz in the VSTS-instance at https://fabrikam.visualstudio.com .</maml:para> </dev:remarks> </command:example> <command:example> <maml:title>---------- EXAMPLE 3 ----------</maml:title> <dev:code>PS C:\> Get-VstsRelease 123</dev:code> <dev:remarks> <maml:para>Get release with ID 123 from the current project.</maml:para> </dev:remarks> </command:example> </command:examples> </command:command> <!-- Cmdlet: Get-VstsReleaseDefinition --> <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10"> <command:details> <command:name>Get-VstsReleaseDefinition</command:name> <command:verb>Get</command:verb> <command:noun>VstsReleaseDefinition</command:noun> <maml:description> <maml:para>Gets the release-definitions from Visual Studio Team Services</maml:para> </maml:description> </command:details> <maml:description> <maml:para>The Get-VstsReleaseDefinition cmdlet gets the release-definitions from a VSTS project.</maml:para> </maml:description> <command:syntax> <!-- Parameter set: __AllParameterSets --> <command:syntaxItem> <maml:name>Get-VstsReleaseDefinition</maml:name> <!-- Parameter: AccessToken --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>AccessToken</maml:name> <maml:description> <maml:para>Personal Access Token (PAT) to login to the VSTS-server. If this is not specified, the access token will be read from the current configuration. The access token cannot be shown using Get-VstsConfiguration, but it is possible to update it by Set-VstsConfiguration. The access token is stored in the windows credential store. In case there is no current access token and the AccessToken argument has not been specified, the cmdlet will prompt for a token.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Project --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Project</maml:name> <maml:description> <maml:para>Project name of the Visual Studio Team Services project. If this is not specified, the project will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the project argument has not been specified, the cmdlet will prompt for a project.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Url --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Url</maml:name> <maml:description> <maml:para>Url of the Visual Studio Team Services instance. If this is not specified, the URL will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the URL argument has not been specified, the cmdlet will prompt for a URL.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> </command:syntaxItem> </command:syntax> <command:parameters> <!-- Parameter: Url --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Url</maml:name> <maml:description> <maml:para>Url of the Visual Studio Team Services instance. If this is not specified, the URL will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the URL argument has not been specified, the cmdlet will prompt for a URL.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Project --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Project</maml:name> <maml:description> <maml:para>Project name of the Visual Studio Team Services project. If this is not specified, the project will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the project argument has not been specified, the cmdlet will prompt for a project.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: AccessToken --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>AccessToken</maml:name> <maml:description> <maml:para>Personal Access Token (PAT) to login to the VSTS-server. If this is not specified, the access token will be read from the current configuration. The access token cannot be shown using Get-VstsConfiguration, but it is possible to update it by Set-VstsConfiguration. The access token is stored in the windows credential store. In case there is no current access token and the AccessToken argument has not been specified, the cmdlet will prompt for a token.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> </command:parameters> <command:inputTypes /> <command:returnValues /> <command:examples> <command:example> <maml:title>---------- EXAMPLE 1 ----------</maml:title> <dev:code>PS C:\> Get-VstsReleaseDefinition</dev:code> <dev:remarks> <maml:para>Returns all release-definitions from the current project.</maml:para> </dev:remarks> </command:example> <command:example> <maml:title>---------- EXAMPLE 2 ----------</maml:title> <dev:code>PS C:\> Get-VstsReleaseDefinition -Url https://fabrikam.visualstudio.com -Project xyz</dev:code> <dev:remarks> <maml:para>Returns all release definitions from the project xyz in the VSTS-instance at https://fabrikam.visualstudio.com .</maml:para> </dev:remarks> </command:example> </command:examples> </command:command> <!-- Cmdlet: Get-VstsRepository --> <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10"> <command:details> <command:name>Get-VstsRepository</command:name> <command:verb>Get</command:verb> <command:noun>VstsRepository</command:noun> <maml:description> <maml:para>Gets the repositories from Visual Studio Team Services</maml:para> </maml:description> </command:details> <maml:description> <maml:para>The Get-VstsRepository cmdlet gets the repositories from a VSTS project.</maml:para> </maml:description> <command:syntax> <!-- Parameter set: __AllParameterSets --> <command:syntaxItem> <maml:name>Get-VstsRepository</maml:name> <!-- Parameter: AccessToken --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>AccessToken</maml:name> <maml:description> <maml:para>Personal Access Token (PAT) to login to the VSTS-server. If this is not specified, the access token will be read from the current configuration. The access token cannot be shown using Get-VstsConfiguration, but it is possible to update it by Set-VstsConfiguration. The access token is stored in the windows credential store. In case there is no current access token and the AccessToken argument has not been specified, the cmdlet will prompt for a token.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Project --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Project</maml:name> <maml:description> <maml:para>Project name of the Visual Studio Team Services project. If this is not specified, the project will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the project argument has not been specified, the cmdlet will prompt for a project.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Url --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Url</maml:name> <maml:description> <maml:para>Url of the Visual Studio Team Services instance. If this is not specified, the URL will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the URL argument has not been specified, the cmdlet will prompt for a URL.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> </command:syntaxItem> </command:syntax> <command:parameters> <!-- Parameter: Url --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Url</maml:name> <maml:description> <maml:para>Url of the Visual Studio Team Services instance. If this is not specified, the URL will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the URL argument has not been specified, the cmdlet will prompt for a URL.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Project --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Project</maml:name> <maml:description> <maml:para>Project name of the Visual Studio Team Services project. If this is not specified, the project will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the project argument has not been specified, the cmdlet will prompt for a project.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: AccessToken --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>AccessToken</maml:name> <maml:description> <maml:para>Personal Access Token (PAT) to login to the VSTS-server. If this is not specified, the access token will be read from the current configuration. The access token cannot be shown using Get-VstsConfiguration, but it is possible to update it by Set-VstsConfiguration. The access token is stored in the windows credential store. In case there is no current access token and the AccessToken argument has not been specified, the cmdlet will prompt for a token.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> </command:parameters> <command:inputTypes /> <command:returnValues /> <command:examples> <command:example> <maml:title>---------- EXAMPLE 1 ----------</maml:title> <dev:code>PS C:\> Get-VstsRepository</dev:code> <dev:remarks> <maml:para>Returns all repositories from the current project.</maml:para> </dev:remarks> </command:example> <command:example> <maml:title>---------- EXAMPLE 2 ----------</maml:title> <dev:code>PS C:\> Get-VstsRepository -Url https://fabrikam.visualstudio.com -Project xyz</dev:code> <dev:remarks> <maml:para>Returns all repositories from the project xyz in the VSTS-instance at https://fabrikam.visualstudio.com .</maml:para> </dev:remarks> </command:example> </command:examples> </command:command> <!-- Cmdlet: Get-VstsWorkItem --> <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10"> <command:details> <command:name>Get-VstsWorkItem</command:name> <command:verb>Get</command:verb> <command:noun>VstsWorkItem</command:noun> </command:details> <command:syntax> <!-- Parameter set: Filter --> <command:syntaxItem> <maml:name>Get-VstsWorkItem</maml:name> <!-- Parameter: AccessToken --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>AccessToken</maml:name> <maml:description> <maml:para>Personal Access Token (PAT) to login to the VSTS-server. If this is not specified, the access token will be read from the current configuration. The access token cannot be shown using Get-VstsConfiguration, but it is possible to update it by Set-VstsConfiguration. The access token is stored in the windows credential store. In case there is no current access token and the AccessToken argument has not been specified, the cmdlet will prompt for a token.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: AssignedToMe --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>AssignedToMe</maml:name> <command:parameterValue required="true">SwitchParameter</command:parameterValue> <dev:type> <maml:name>System.Management.Automation.SwitchParameter</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>False</dev:defaultValue> </command:parameter> <!-- Parameter: CurrentIteration --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>CurrentIteration</maml:name> <command:parameterValue required="true">SwitchParameter</command:parameterValue> <dev:type> <maml:name>System.Management.Automation.SwitchParameter</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>False</dev:defaultValue> </command:parameter> <!-- Parameter: Project --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Project</maml:name> <maml:description> <maml:para>Project name of the Visual Studio Team Services project. If this is not specified, the project will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the project argument has not been specified, the cmdlet will prompt for a project.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: RecentlyChanged --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>RecentlyChanged</maml:name> <command:parameterValue required="true">SwitchParameter</command:parameterValue> <dev:type> <maml:name>System.Management.Automation.SwitchParameter</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>False</dev:defaultValue> </command:parameter> <!-- Parameter: RecentlyCreated --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>RecentlyCreated</maml:name> <command:parameterValue required="true">SwitchParameter</command:parameterValue> <dev:type> <maml:name>System.Management.Automation.SwitchParameter</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>False</dev:defaultValue> </command:parameter> <!-- Parameter: State --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>State</maml:name> <command:parameterValue required="true">string[]</command:parameterValue> <dev:type> <maml:name>System.String[]</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Type --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Type</maml:name> <command:parameterValue required="true">string[]</command:parameterValue> <dev:type> <maml:name>System.String[]</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Url --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Url</maml:name> <maml:description> <maml:para>Url of the Visual Studio Team Services instance. If this is not specified, the URL will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the URL argument has not been specified, the cmdlet will prompt for a URL.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> </command:syntaxItem> <!-- Parameter set: Id --> <command:syntaxItem> <maml:name>Get-VstsWorkItem</maml:name> <!-- Parameter: Id --> <command:parameter required="false" globbing="false" pipelineInput="false" position="0" aliases="Ids"> <maml:name>Id</maml:name> <command:parameterValue required="true">int[]</command:parameterValue> <dev:type> <maml:name>System.Int32[]</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: AccessToken --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>AccessToken</maml:name> <maml:description> <maml:para>Personal Access Token (PAT) to login to the VSTS-server. If this is not specified, the access token will be read from the current configuration. The access token cannot be shown using Get-VstsConfiguration, but it is possible to update it by Set-VstsConfiguration. The access token is stored in the windows credential store. In case there is no current access token and the AccessToken argument has not been specified, the cmdlet will prompt for a token.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Project --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Project</maml:name> <maml:description> <maml:para>Project name of the Visual Studio Team Services project. If this is not specified, the project will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the project argument has not been specified, the cmdlet will prompt for a project.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Url --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Url</maml:name> <maml:description> <maml:para>Url of the Visual Studio Team Services instance. If this is not specified, the URL will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the URL argument has not been specified, the cmdlet will prompt for a URL.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> </command:syntaxItem> <!-- Parameter set: Build --> <command:syntaxItem> <maml:name>Get-VstsWorkItem</maml:name> <!-- Parameter: AccessToken --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>AccessToken</maml:name> <maml:description> <maml:para>Personal Access Token (PAT) to login to the VSTS-server. If this is not specified, the access token will be read from the current configuration. The access token cannot be shown using Get-VstsConfiguration, but it is possible to update it by Set-VstsConfiguration. The access token is stored in the windows credential store. In case there is no current access token and the AccessToken argument has not been specified, the cmdlet will prompt for a token.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: BuildId --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>BuildId</maml:name> <command:parameterValue required="true">int</command:parameterValue> <dev:type> <maml:name>System.Int32</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>0</dev:defaultValue> </command:parameter> <!-- Parameter: Project --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Project</maml:name> <maml:description> <maml:para>Project name of the Visual Studio Team Services project. If this is not specified, the project will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the project argument has not been specified, the cmdlet will prompt for a project.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Url --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Url</maml:name> <maml:description> <maml:para>Url of the Visual Studio Team Services instance. If this is not specified, the URL will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the URL argument has not been specified, the cmdlet will prompt for a URL.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> </command:syntaxItem> </command:syntax> <command:parameters> <!-- Parameter: Type --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Type</maml:name> <command:parameterValue required="true">string[]</command:parameterValue> <dev:type> <maml:name>System.String[]</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: State --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>State</maml:name> <command:parameterValue required="true">string[]</command:parameterValue> <dev:type> <maml:name>System.String[]</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Id --> <command:parameter required="false" globbing="false" pipelineInput="false" position="0" aliases="Ids"> <maml:name>Id</maml:name> <command:parameterValue required="true">int[]</command:parameterValue> <dev:type> <maml:name>System.Int32[]</maml:name> <maml:uri /> </dev:type> </command:parameter> <command:parameter required="false" globbing="false" pipelineInput="false" position="0" aliases="Ids"> <maml:name>Ids</maml:name> <command:parameterValue required="true">int[]</command:parameterValue> <dev:type> <maml:name>System.Int32[]</maml:name> <maml:uri /> </dev:type> <maml:description> <maml:para>This is an alias of the Id parameter.</maml:para> </maml:description> </command:parameter> <!-- Parameter: BuildId --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>BuildId</maml:name> <command:parameterValue required="true">int</command:parameterValue> <dev:type> <maml:name>System.Int32</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>0</dev:defaultValue> </command:parameter> <!-- Parameter: RecentlyChanged --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>RecentlyChanged</maml:name> <command:parameterValue required="true">SwitchParameter</command:parameterValue> <dev:type> <maml:name>System.Management.Automation.SwitchParameter</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>False</dev:defaultValue> </command:parameter> <!-- Parameter: RecentlyCreated --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>RecentlyCreated</maml:name> <command:parameterValue required="true">SwitchParameter</command:parameterValue> <dev:type> <maml:name>System.Management.Automation.SwitchParameter</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>False</dev:defaultValue> </command:parameter> <!-- Parameter: AssignedToMe --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>AssignedToMe</maml:name> <command:parameterValue required="true">SwitchParameter</command:parameterValue> <dev:type> <maml:name>System.Management.Automation.SwitchParameter</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>False</dev:defaultValue> </command:parameter> <!-- Parameter: CurrentIteration --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>CurrentIteration</maml:name> <command:parameterValue required="true">SwitchParameter</command:parameterValue> <dev:type> <maml:name>System.Management.Automation.SwitchParameter</maml:name> <maml:uri /> </dev:type> <dev:defaultValue>False</dev:defaultValue> </command:parameter> <!-- Parameter: Url --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Url</maml:name> <maml:description> <maml:para>Url of the Visual Studio Team Services instance. If this is not specified, the URL will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the URL argument has not been specified, the cmdlet will prompt for a URL.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Project --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Project</maml:name> <maml:description> <maml:para>Project name of the Visual Studio Team Services project. If this is not specified, the project will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the project argument has not been specified, the cmdlet will prompt for a project.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: AccessToken --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>AccessToken</maml:name> <maml:description> <maml:para>Personal Access Token (PAT) to login to the VSTS-server. If this is not specified, the access token will be read from the current configuration. The access token cannot be shown using Get-VstsConfiguration, but it is possible to update it by Set-VstsConfiguration. The access token is stored in the windows credential store. In case there is no current access token and the AccessToken argument has not been specified, the cmdlet will prompt for a token.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> </command:parameters> <command:inputTypes /> <command:returnValues /> </command:command> <!-- Cmdlet: New-VstsWorkItem --> <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10"> <command:details> <command:name>New-VstsWorkItem</command:name> <command:verb>New</command:verb> <command:noun>VstsWorkItem</command:noun> </command:details> <command:syntax> <!-- Parameter set: __AllParameterSets --> <command:syntaxItem> <maml:name>New-VstsWorkItem</maml:name> <!-- Parameter: Type --> <command:parameter required="true" globbing="false" pipelineInput="false" position="named"> <maml:name>Type</maml:name> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: AccessToken --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>AccessToken</maml:name> <maml:description> <maml:para>Personal Access Token (PAT) to login to the VSTS-server. If this is not specified, the access token will be read from the current configuration. The access token cannot be shown using Get-VstsConfiguration, but it is possible to update it by Set-VstsConfiguration. The access token is stored in the windows credential store. In case there is no current access token and the AccessToken argument has not been specified, the cmdlet will prompt for a token.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Project --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Project</maml:name> <maml:description> <maml:para>Project name of the Visual Studio Team Services project. If this is not specified, the project will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the project argument has not been specified, the cmdlet will prompt for a project.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Url --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Url</maml:name> <maml:description> <maml:para>Url of the Visual Studio Team Services instance. If this is not specified, the URL will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the URL argument has not been specified, the cmdlet will prompt for a URL.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> </command:syntaxItem> </command:syntax> <command:parameters> <!-- Parameter: Type --> <command:parameter required="true" globbing="false" pipelineInput="false" position="named"> <maml:name>Type</maml:name> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Url --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Url</maml:name> <maml:description> <maml:para>Url of the Visual Studio Team Services instance. If this is not specified, the URL will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the URL argument has not been specified, the cmdlet will prompt for a URL.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Project --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Project</maml:name> <maml:description> <maml:para>Project name of the Visual Studio Team Services project. If this is not specified, the project will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the project argument has not been specified, the cmdlet will prompt for a project.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: AccessToken --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>AccessToken</maml:name> <maml:description> <maml:para>Personal Access Token (PAT) to login to the VSTS-server. If this is not specified, the access token will be read from the current configuration. The access token cannot be shown using Get-VstsConfiguration, but it is possible to update it by Set-VstsConfiguration. The access token is stored in the windows credential store. In case there is no current access token and the AccessToken argument has not been specified, the cmdlet will prompt for a token.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> </command:parameters> <command:inputTypes /> <command:returnValues /> </command:command> <!-- Cmdlet: Save-VstsWorkItem --> <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10"> <command:details> <command:name>Save-VstsWorkItem</command:name> <command:verb>Save</command:verb> <command:noun>VstsWorkItem</command:noun> </command:details> <command:syntax> <!-- Parameter set: __AllParameterSets --> <command:syntaxItem> <maml:name>Save-VstsWorkItem</maml:name> <!-- Parameter: Items --> <command:parameter required="false" globbing="false" pipelineInput="true (ByValue)" position="1"> <maml:name>Items</maml:name> <command:parameterValue required="true">VstsWorkItem[]</command:parameterValue> <dev:type> <maml:name>PoshVsts.VstsWorkItem[]</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: AccessToken --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>AccessToken</maml:name> <maml:description> <maml:para>Personal Access Token (PAT) to login to the VSTS-server. If this is not specified, the access token will be read from the current configuration. The access token cannot be shown using Get-VstsConfiguration, but it is possible to update it by Set-VstsConfiguration. The access token is stored in the windows credential store. In case there is no current access token and the AccessToken argument has not been specified, the cmdlet will prompt for a token.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Project --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Project</maml:name> <maml:description> <maml:para>Project name of the Visual Studio Team Services project. If this is not specified, the project will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the project argument has not been specified, the cmdlet will prompt for a project.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Url --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Url</maml:name> <maml:description> <maml:para>Url of the Visual Studio Team Services instance. If this is not specified, the URL will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the URL argument has not been specified, the cmdlet will prompt for a URL.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> </command:syntaxItem> </command:syntax> <command:parameters> <!-- Parameter: Items --> <command:parameter required="false" globbing="false" pipelineInput="true (ByValue)" position="1"> <maml:name>Items</maml:name> <command:parameterValue required="true">VstsWorkItem[]</command:parameterValue> <dev:type> <maml:name>PoshVsts.VstsWorkItem[]</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Url --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Url</maml:name> <maml:description> <maml:para>Url of the Visual Studio Team Services instance. If this is not specified, the URL will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the URL argument has not been specified, the cmdlet will prompt for a URL.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Project --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Project</maml:name> <maml:description> <maml:para>Project name of the Visual Studio Team Services project. If this is not specified, the project will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the project argument has not been specified, the cmdlet will prompt for a project.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: AccessToken --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>AccessToken</maml:name> <maml:description> <maml:para>Personal Access Token (PAT) to login to the VSTS-server. If this is not specified, the access token will be read from the current configuration. The access token cannot be shown using Get-VstsConfiguration, but it is possible to update it by Set-VstsConfiguration. The access token is stored in the windows credential store. In case there is no current access token and the AccessToken argument has not been specified, the cmdlet will prompt for a token.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> </command:parameters> <command:inputTypes> <command:inputType> <dev:type> <maml:name>PoshVsts.VstsWorkItem[]</maml:name> <maml:uri /> </dev:type> </command:inputType> </command:inputTypes> <command:returnValues /> </command:command> <!-- Cmdlet: Get-VstsWorkItemState --> <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10"> <command:details> <command:name>Get-VstsWorkItemState</command:name> <command:verb>Get</command:verb> <command:noun>VstsWorkItemState</command:noun> </command:details> <command:syntax> <!-- Parameter set: __AllParameterSets --> <command:syntaxItem> <maml:name>Get-VstsWorkItemState</maml:name> <!-- Parameter: AccessToken --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>AccessToken</maml:name> <maml:description> <maml:para>Personal Access Token (PAT) to login to the VSTS-server. If this is not specified, the access token will be read from the current configuration. The access token cannot be shown using Get-VstsConfiguration, but it is possible to update it by Set-VstsConfiguration. The access token is stored in the windows credential store. In case there is no current access token and the AccessToken argument has not been specified, the cmdlet will prompt for a token.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Project --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Project</maml:name> <maml:description> <maml:para>Project name of the Visual Studio Team Services project. If this is not specified, the project will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the project argument has not been specified, the cmdlet will prompt for a project.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Url --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Url</maml:name> <maml:description> <maml:para>Url of the Visual Studio Team Services instance. If this is not specified, the URL will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the URL argument has not been specified, the cmdlet will prompt for a URL.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> </command:syntaxItem> </command:syntax> <command:parameters> <!-- Parameter: Url --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Url</maml:name> <maml:description> <maml:para>Url of the Visual Studio Team Services instance. If this is not specified, the URL will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the URL argument has not been specified, the cmdlet will prompt for a URL.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Project --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Project</maml:name> <maml:description> <maml:para>Project name of the Visual Studio Team Services project. If this is not specified, the project will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the project argument has not been specified, the cmdlet will prompt for a project.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: AccessToken --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>AccessToken</maml:name> <maml:description> <maml:para>Personal Access Token (PAT) to login to the VSTS-server. If this is not specified, the access token will be read from the current configuration. The access token cannot be shown using Get-VstsConfiguration, but it is possible to update it by Set-VstsConfiguration. The access token is stored in the windows credential store. In case there is no current access token and the AccessToken argument has not been specified, the cmdlet will prompt for a token.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> </command:parameters> <command:inputTypes /> <command:returnValues /> </command:command> <!-- Cmdlet: Get-VstsWorkItemType --> <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10"> <command:details> <command:name>Get-VstsWorkItemType</command:name> <command:verb>Get</command:verb> <command:noun>VstsWorkItemType</command:noun> </command:details> <command:syntax> <!-- Parameter set: __AllParameterSets --> <command:syntaxItem> <maml:name>Get-VstsWorkItemType</maml:name> <!-- Parameter: AccessToken --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>AccessToken</maml:name> <maml:description> <maml:para>Personal Access Token (PAT) to login to the VSTS-server. If this is not specified, the access token will be read from the current configuration. The access token cannot be shown using Get-VstsConfiguration, but it is possible to update it by Set-VstsConfiguration. The access token is stored in the windows credential store. In case there is no current access token and the AccessToken argument has not been specified, the cmdlet will prompt for a token.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Project --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Project</maml:name> <maml:description> <maml:para>Project name of the Visual Studio Team Services project. If this is not specified, the project will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the project argument has not been specified, the cmdlet will prompt for a project.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Url --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Url</maml:name> <maml:description> <maml:para>Url of the Visual Studio Team Services instance. If this is not specified, the URL will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the URL argument has not been specified, the cmdlet will prompt for a URL.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> </command:syntaxItem> </command:syntax> <command:parameters> <!-- Parameter: Url --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Url</maml:name> <maml:description> <maml:para>Url of the Visual Studio Team Services instance. If this is not specified, the URL will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the URL argument has not been specified, the cmdlet will prompt for a URL.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: Project --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>Project</maml:name> <maml:description> <maml:para>Project name of the Visual Studio Team Services project. If this is not specified, the project will be read from the current configuration, which can be shown using Get-VstsConfiguration and update by Set-VstsConfiguration. The configuration is stored in a file named '.poshVsts' the user directory. In case there is no current configuration and the project argument has not been specified, the cmdlet will prompt for a project.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> <!-- Parameter: AccessToken --> <command:parameter required="false" globbing="false" pipelineInput="false" position="named"> <maml:name>AccessToken</maml:name> <maml:description> <maml:para>Personal Access Token (PAT) to login to the VSTS-server. If this is not specified, the access token will be read from the current configuration. The access token cannot be shown using Get-VstsConfiguration, but it is possible to update it by Set-VstsConfiguration. The access token is stored in the windows credential store. In case there is no current access token and the AccessToken argument has not been specified, the cmdlet will prompt for a token.</maml:para> </maml:description> <command:parameterValue required="true">string</command:parameterValue> <dev:type> <maml:name>System.String</maml:name> <maml:uri /> </dev:type> </command:parameter> </command:parameters> <command:inputTypes /> <command:returnValues /> </command:command> </helpItems> |