To check in a file, you must submit a changelistAn atomic change transaction in Helix. The changes specified in the changelist are not stored in the depot until the changelist is submitted to the depot.. Whenever you mark files for add or delete, check them out, integrateTo compare two sets of files (for example, two codeline branches) and determine which changes in one set apply to the other; determine if the changes have already been propagated; propagate any outstanding changes. (merge or copy), or schedule them for resolveThe process you use to reconcile the differences between two revisions of a file. You can choose to resolve conflicts by selecting a file to be submitted or by merging the contents of conflicting files., the files are added to changelists. Helix Core changelists are lists of actions to be performed on files. The actions in the changelist are performed when you submitTo send a pending changelist and changed files to the Helix Core server for processing. the changelist. Pending changelistsA changelist that has not been submitted. are changelists that have yet to be submitted. Changelists are assigned unique numbers by the Perforce service. In addition, a default changelistThe changelist used by commands, unless a numbered changelist is specified. A default pending changelist is created automatically when a file is opened for edit. is maintained for each client workspaceDirectories on your machine where you work on file revisions that are managed by Helix. By default this name is set to the name of the machine on which your client workspace is located; to override the default name, set the P4CLIENT environment variable. Client workspaces, labels, and branch specifications cannot share the same name.. If submission of the default changelist fails, the Perforce service assigns it a numberThe unique numeric identifier of a changelist..