Submitting work

You always need to give a description of the changes you are about to submit. This description is given at a different moment in Perforce and Git.

Perforce

Use of an explicit changelist

You can create an explicit changelist and give it a description before adding changes to it:

$ p4 change
<description>

You then submit a single "changelist" to the depot:

$ p4 submit <changelist>

Use of the default changelist

If you use the default pending changelist (when you don't specify a changelist on a checkout), you provide a description at the submission step:

$ p4 submit -d <description>

Git

(image source: atlassian.com)

In Git, it's only after you added your changes in your stage that you commit them with a description:

$ git commit -m <description>

You can create more commits before any submission.

REMINDER Git is a distributed version control system. At this step you only added commit information in your local repo (your .git folder). Nothing is actually transmitted to a remote server.

You submit your work to a another repository by pushing a local branch to remote one:

$ git push <repository> <local_branch>:<remote-branch>

Branches will be covered in details in the next courses.

Summary

You learned:

• perforce changelist creation and description vs git staging and commit message
• perforce submit vs git push