checkin

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 supplying 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

[ -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.

[ -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