Checking in unresolved changes
Engineering Workflow Management source control uses an optimistic locking model that does not require a check-out operation before you can modify files or folders. All files in a sandbox are normally writable. Modified files remain private to your repository workspace until you deliver them.
About this task
Engineering Workflow Management source control tracks the changes that you make in your sandbox and displays them in the Pending Changes view. Each modified component in a workspace can include an Unresolved folder, an Outgoing folder, or both. These folders contain the changes you have made.
- Expand the Unresolved folder to
see its contents.
- To check in the entire set of unresolved changes to the current change set, right-click the Unresolved folder and click Check-in all.
- To check in an individual item in the Unresolved folder, right-click it, click Check-in, and click an existing change set to receive the change, or click New change set to create a change set. (A file or folder in a component cannot be part of more than one active change set. When a file or folder is included in an active change set, all changes to it become part of that change set whether or not the change set is current, and changes to that file or folder cannot be explicitly checked in to a new change set until the active change set that includes it is completed.)
- Optional: On Windows, to automatically detect changes
made outside of Eclipse:
- Click .
- On the Preferences page, navigate to .
- On the Local Changes page, select Automatically detect changes.
- Click Apply. Note: To preserve history, use Eclipse to rename or move files and folders.