Submitting Source Control Files—Perforce Helix Core

When you are finished editing files, you can submit them to source control. Submitting a file overwrites the old copy of the file in the source control database with the new one from your local machine. So even if others will not be working on that file, it is a good idea to periodically submit files so that you have a backup in source control.

How to Submit Files to Source Control

  1. Do one of the following, depending on the part of the user interface you are using:

    • Ribbon Select Source Control > Submit (for selected files) or Source Control > Submit All (for all files in the project).

    • Right-Click In the File List, right-click the file you want to submit and select Source Control > Submit (for selected files) or Source Control > Project > Submit All (for all files in the project).

    The Submit dialog opens. The selected files are listed with check boxes next to them.

  2. (Optional) In the Comment field, enter an optional comment tied to the submit. This enables you to keep an audit trail for a file. The comment can then be viewed from the History dialog, which can be accessed from the Source Control Explorer, the Source Control ribbon, or the Source Control button .

  3. (Optional) If you want to see all files with pending changes (rather than only those you selected), click .

  4. Make sure to click the check box next to each file you want to check in so that it contains a check mark.
  5. If you want to keep the files checked out of source control, select Keep Checked Out. Doing this will overwrite the source control copies of the files so that they have the latest changes, but it lets you continue working on the files. This is a useful option if you are the only author working on the files in question.

  6. Click Submit.

    If no other users have also made changes to the file and submitted it while you were working on it, your version of the file is submitted.

    However, if that is not the case, the Resolve Version Conflict dialog opens to let you know that another user has already submitted the file with changes. You can merge the files automatically if there are no conflicting changes (i.e., changes do not occur in the same location in the file). If there are conflicting changes, you can use the Merge Changes dialog to determine how changes are merged. See Merging Source Control Files—Perforce Helix Core.

How to Submit Files to Source Control Using the Explorer

  1. Select View > Source Control Explorer. The Source Control Explorer opens.

  2. From the drop-down or the Home pane, select Pending Changes.

    The Pending Changes pane opens. Files that will be committed are listed under Included Changes, and files that will not be committed are listed under Excluded Changes. You can identify edited files because [modified] is displayed next to the file name.

    Note When you check out a file in source control, you may sometimes see a SKL file alongside the XLF and original files. This skeleton file is a placeholder file. Be sure to submit all three associated files together. Submitting just the SKL file may result in errors.

  3. (Optional) In the Comment field, enter an optional comment tied to the submit. This enables you to keep an audit trail for a file. The comment can then be viewed from the History dialog, which can be accessed from the Source Control Explorer, the Source Control ribbon, or the Source Control button ..
  4. (Optional) If you want to select the files or folders that you include in the submit, right-click a file or folder and select one of the following options from the context menu.

    • Exclude Excludes the selected file from the submit

    • Exclude Unselected Excludes all unselected files from the submit

    • Include Includes the selected file in the submit

    • Include Unselected Includes all unselected files in the submit

  5. Click Submit Included to submit all of the files in the Included Changes list.

    If no other users have also made changes to the file and submitted it while you were working on it, your version of the file is submitted.

    However, if that is not the case, the Resolve Version Conflict dialog opens to let you know that another user has already submitted the file with changes. You can merge the files automatically if there are no conflicting changes (i.e., changes do not occur in the same location in the file). If there are conflicting changes, you can use the Merge Changes dialog to determine how changes are merged. See Merging Source Control Files—Perforce Helix Core.