Description - Mks.com

si lock
locks project members
SYNOPSIS
si lock [--[no|confirm]branch] [--[no|confirm]branchVariant]
[(--cpid ID|--changePackageId=ID)] [--issueId =ID] [(-r rev|--revision=rev)]
[(-R|--[no|confirm]recurse)] [--filter=filteroptions] [(-P project|--project=project)]
[(-S sandbox|--sandbox=sandbox)] [--devpath=path] [--hostname=server]
[--port=number] [--password=password] [--user=name] [(-?|--usage)]
[(-F file|--selectionFile=file)] [(-N|--no)] [(-Y|--yes)] [--[no]batch] [--cwd=directory]
[--forceConfirm=[yes|no]] [(-g|--gui)] [--quiet] [--settingsUI=[gui|default]]
[--status=[none|gui|default]] member...
DESCRIPTION
si lock locks one or more project members. If no members are specified, si lock applies to all
project members. By default, the member revision is locked and not necessarily the working
revision, if in a sandbox.
This is purely a project operation -- if performed in a sandbox, no memory of what revision was
locked is maintained in the sandbox.
Depending on the locking policy configured by your administrator, you may hold a lock on only one
revision of a particular member at a time. It is not an "error" to relock an already locked member.
If the target revision is already locked by a user other than yourself, then specifying the --branch
option creates a branch revision and locks it. Otherwise, you cannot lock the revision at all.
Options
This command takes the universal options available to all si commands, as well as some general
options. See the options reference page for descriptions.
--[no|confirm]branch
controls whether to create a branch revision if the target revision is already locked by a user
other than yourself.
For details on branch revisions, see the si ci reference page.
--[no|confirm]branchVariant
controls whether to create a branch off of the revision you are locking, if you are working in a
variant sandbox. This is useful for keeping changes in the variant separate from changes
149 of 457