|
|
|
|
|
|
|
|
|
|
- Overview
- Retrieving all the elements
- Checking in all the elements
SCM: Retrieving and Checking in all
When developing a project in the SCM, you may need to retrieve all the elements from the repository, or to check all the elements stored locally back into the repository.
Retrieving all the elements The "Retrieve all" option retrieves all new versions of project elements present in the repository. Elements currently checked out by the user are not included. This option updates the local version with all the elements currently in the repository. This window includes the following options: - "Changes": Shows the changes between the element stored locally and the corresponding element on the repository.
- "History": Opens a history of actions performed on the selected element.
- "Properties": Opens a window with the details of the selected element.
- "Delete": Deletes the element locally instead of retrieving it.
 New in version 2025"Filter binary differences": Grays out elements for which there are no code or UI changes in the repository. These grayed-out elements are only different on a binary level (for example, changing the window from version N-1 to version N). Grayed-out items are automatically retrieved.
New in version 2025When checked, the "Recompile project" option recompiles the project immediately after retrieving elements from the SCM repository. Checking in all the elements The "Check all in" option checks all the checked-out project elements into the SCM repository. You can uncheck the elements you don't want to check back in. This window includes the following options: - "My changes": Gets the list of changes you made since the element was last checked out from the repository.
- "Compare": Shows the differences between the local element and the one present in the repository.
- "History": Opens a history of actions performed on the selected element.
- "Properties": Opens a window with the details of the selected element.
- "Merge": If a conflict occurs when checking in the selected element, opens the comparison window to allow you to merge changes.
New in version 2025"Filter binary differences": Grays out elements for which there are no code or UI changes. These grayed-out elements are only different on a binary level (for example, changing the window from version N-1 to version N). Grayed-out items are automatically checked in.
You can also select or deselect all elements.
The "Non-conflicting elements" button selects all the elements that can be checked in without conflicts. This allows you to focus on the conflicting elements. The tabs at the bottom of the window allow you to associate the check-in of selected elements with: - one or more tasks,
- one or more incidents,
- a comment.
When checked, the "Keep checked-out elements" option checks selected elements into the repository, but also keeps their local version. Note: Depending on the options selected, this window is also displayed when the project is closed.
This page is also available for…
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|