Check in locally modified files, adding them to the current
change set
Purpose
The scm checkin subcommand
checks in one or more locally modified files or folders, adding them
to the current change set in the repository workspace.
Synopsis
- To run scm checkin after you have used scm login to
create stored credentials for the repository linked to local workspace
specified by -d:
scm checkin { [ -d | --dir ] workspace-path } path ...
- To run scm checkin and supply credentials
(for the repository linked to local workspace specified by -d)
on the command line:
scm checkin [ -u | --username ] user ID in repository [ -P | --password ] password for user ID in repository { [ -d | --dir ] workspace-path } path ...
Options and arguments
- [ -c
| --change-set ] arg
- Alias or UUID of target change set.
Changes can be checked in to another change set.
- [ -C | --delim-consistent ]
- Force any file with inconsistent line
delimiters to use the preferred line delimiter (depending on file
properties).
- [ -n
| --delim-none ]
- Force any file with inconsistent line
delimiters to be given the NONE delimiter preference (disabling line
delimiter checks).
- [ -d | --dir ] workspace-path
- The path name of a local workspace created
by scm load or scm share.
This subcommand runs with workspace-path set as
the current working directory. You can omit this option if the current
working directory is in a local workspace.
- [ -d
| --directory ] arg
- Run in the named directory.
- [ -P | --password ] password for user ID in repository
- The password for the specified user ID in
the named repository. If this option is not included on the command
line, you are prompted for a password. If you specified a repository
URI or nickname for which you have stored credentials using the scm
login command, this option is ignored.
- [ -u | --username ] user ID in repository
- Specifies a user ID that exists in the named
repository. If you specified a repository URI or nickname for which
you have stored credentials using the scm login command,
this option is ignored.
- path ...
- A space-separated list of path names to check in. Each path must
be in a local workspace. If a -d option was used
to specify a local directory where scm checkin should
run, all path arguments are interpreted relative
to that directory. Otherwise, path arguments are
interpreted relative to the current working directory. If path is
a directory, all unresolved files in the directory and its subdirectories
are checked in.
Examples
Working in a local workspace, modify
the file
com.example.hellojazz.rcp.ui\src\com\example\hellojazz\rcp\ui\actions\HelloJazzAction.java.
After you save the file,
scm status output
indicates an unresolved (modified but not checked in) file.
C:\local-workspaces\HelloJazz>scm status
Workspace: (1101) "HelloJazz" <-> (1102) "HelloJazz Stream"
Component: (1103) "HelloJazz"
Baseline: (1104) 2 "base"
Unresolved:
-c /com.example.hellojazz.rcp.ui/src/com/example/hellojazz/rcp/ui/actions>
Run
scm checkin to
check in the file and create a change set.
C:\local-workspaces\HelloJazz>scm checkin com.example.hellojazz.rcp.ui\src\com\example\hellojazz\rcp\ui\actions\HelloJazzAction.java
Committing...
Workspace: (1101) "HelloJazz" <-> (1102) "HelloJazz Stream"
Component: (1103) "HelloJazz"
Outgoing:
Change sets:
(1105) --@ <No comment>