si revert

CLI Reference > Configuration Management Commands > si revert

si revert

overwrites a sandbox file with a fresh copy of the working file, discarding changes

Synopsis

Description

si revert restores a working file to a state before changes were made, by overwriting the Sandbox file with a fresh copy of the working file at the same revision you currently have in your Sandbox, not the member revision. If you had the member locked, it is unlocked.

If the revision you have locked is not the working revision, the lock is retained.

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|un]expand

controls whether to expand, unexpand, or ignore keywords in the member file. Keyword expansion is only available in text archives, not binary archives. For descriptions of the Integrity Lifecycle Manager keywords, see the Integrity Lifecycle Manager Help Center. Possible keywords are:

$Author: Taherali, Khuzema (ktaherali) $
$CompanyInfo$
$Date: 2017/02/13 13:04:52IST $
$Header: si_revert.dita 1.5 2017/02/13 13:04:52IST Taherali, Khuzema (ktaherali) Exp $
$Id: si_revert.dita 1.5 2017/02/13 13:04:52IST Taherali, Khuzema (ktaherali) Exp $
$Locker: $
$Log: si_revert.dita $
Revision 1.5 2017/02/13 13:04:52IST Taherali, Khuzema (ktaherali)

Revision 1.3 2015/12/01 02:53:08IST Warner, Carrie (cwarner)
XML tagging fixes
Revision 1.2 2015/11/30 15:01:45EST Warner, Carrie (cwarner)
XML tagging fixes
Revision 1.1 2015/10/29 10:25:00EDT Flett, David (dflett)
Initial revision
Member added to project /rd/doc/Strategic/xmldocs/en/int-man_pages/si_ref/project.pj
$Revision: 1.5 $
$Name: $
$ProjectLabel: $
$ProjectName: /rd/doc/Strategic/xmldocs/en/int-man_pages/si_ref/project.pj $
$ProjectSetting $
$ProjectRevision: Last Checkpoint: 1.1.1.790 $
$RCSfile: si_revert.dita $
$Revision: 1.5 $
$SandboxSetting $
$Setting $
$Source: si_revert.dita $
$State: Exp $

• -f

overwrites the working file if it has changed since it was last checked in. This is equivalent to specifying --overwriteChanged.

• --[no|confirm]overwriteChanged

controls whether to overwrite the working file if it has changed since it was last checked in.

--overwriteChanged means always overwrite

--nooverwriteChanged means never overwrite

--confirmoverwriteChanged means always ask before overwriting. When asked to confirm overwriting the working file, you have the option of specifying y, n or d. Specifying d displays the differences between the member's working file and the revision it is being reverted to.

Specifying the --yes or --no options automatically answers y or n to the confirmation question, and also automatically answers y orn to all questions asked.

• --[no|confirm]removeOutOfScope

controls whether to remove a current member's working file if it does not match the Sandbox scope definition, for example, if the scope definition or member changes (such as modified member attributes). Sandbox Scope defines what project members are included in the Sandbox, transferring specific members from the Integrity Lifecycle Manager Server to the Sandbox directory when the Sandbox is created and controlling what members display in the Sandbox view.

--removeOutOfScope means always remove the working file if it does not match the Sandbox scope.

--noremoveOutOfScope means never remove the working file if it does not match the Sandbox scope.

--confirmremoveOutOfScope means always ask before removing the working file if it does not match the Sandbox scope. When asked to confirm removing the working file, you have the option of specifying y, n or d. Specifying d displays the differences between the member's working file and the revision it is being reverted to.

Specifying the --yes or --no options automatically answers y or n to the confirmation question, and also automatically answers y orn to all questions asked.

• --[no|confirm]overwriteDeferred

controls whether to overwrite the working file if there is a deferred operation on the member.

--overwriteDeferred means always overwrite

--nooverwriteDeferred means never overwrite

--confirmoverwriteDeferred means always ask before overwriting. When asked to confirm overwriting the working file, you have the option of specifying y, n or d. Specifying d displays the differences between the member's working file and the revision it is being reverted to.

Specifying the --yes or --no options automatically answers y or n to the confirmation question, and also automatically answers y orn to all questions asked.

• --[no]overwriteUnchanged

controls whether to overwrite files that have not been modified in the sandbox. This may be useful for forcing files to pick up new keyword expansions or timestamps even if their content has not changed.

• --[no]restoreTimestamp

controls whether to restore the timestamp of the working file to the timestamp of the revision in the member history.

• sandbox member...

identifies a specific member; use spaces to specify more than one member.

If you specify an out of scope member with no working file, the revert operation does not create a working file for the member. For more information on Sandbox scope, see the si configuresandbox and si createsandbox commands.

Diagnostics

See the diagnostics reference page for possible exit status values.

Preferences

Using si setprefs or si viewprefs, you are able to set or view the preference keys for this command.