View commit details in AWS CodeCommit

To browse the history of commits

1. Open the CodeCommit console at https://console.aws.amazon.com/codesuite/codecommit/home.

2. In Repositories, choose the repository for which you want to review the commit history.

3. In the navigation pane, choose Commits. In the commit history view, a history of commits for the repository in the default branch is displayed, in reverse chronological order of the commit date. Date and time are in coordinated universal time (UTC). You can view the commit history of a different branch by choosing the view selector button and then choosing a branch from the list. If you are using tags in your repository, you can view a commit with a specific tag and its parents by choosing that tag in the view selector button.

   

4. To view the difference between a commit and its parent, and to see any comments on the changes, choose the abbreviated commit ID. For more information, see Compare a commit to its parent and Comment on a commit. To view the difference between a commit and any other commit specifier, including a branch, tag, or commit ID, see Compare any two commit specifiers.

5. Do one or more of the following:

   • To view the date and time a change was made, hover over the commit date.

   • To view the full commit ID, copy and then paste it into a text editor or other location. To copy it, choose Copy ID.

   • To view the code as it was at the time of a commit, choose Browse. The contents of the repository as they were at the time of that commit is displayed in the Code view. The view selector button displays the abbreviated commit ID instead of a branch or tag.

To view a graph of commits

1. Open the CodeCommit console at https://console.aws.amazon.com/codesuite/codecommit/home.

2. In Repositories, choose the repository for which you want to view a commit graph.

3. In the navigation pane, choose Commits, and then choose the Commit visualizer tab.

   

   In the commit graph, the abbreviated commit ID and the subject for each commit message appears next to that point in the graph.

   Note

   The graph can display up to 35 branches on a page. If there are more than 35 branches, the graph is too complex to display. You can simplify the view in two ways:

   • By using the view selector button to show the graph for a specific branch.

   • By pasting a full commit ID into the search box to render the graph from that commit.

4. To render a new graph from a commit, choose the point in the graph that corresponds to that commit. The view selector button changes to the abbreviated commit ID.

   

1. Run the aws codecommit get-commit command, specifying:

   • The name of the CodeCommit repository (with the --repository-name option).

   • The full commit ID.

   For example, to view information about a commit with the ID 317f8570EXAMPLE in a CodeCommit repository named MyDemoRepo:

   aws codecommit get-commit  --repository-name MyDemoRepo  --commit-id 317f8570EXAMPLE 

2. If successful, the output of this command includes the following:

   • Information about the author of the commit (as configured in Git), including the date in timestamp format and the coordinated universal time (UTC) offset.

   • Information about the committer (as configured in Git) including the date in timestamp format and the UTC offset.

   • The ID of the Git tree where the commit exists.

   • The commit ID of the parent commit.

   • The commit message.

   Here is some example output, based on the preceding example command:

   {
       "commit": {
           "additionalData": "",
           "committer": {
               "date": "1484167798 -0800",
               "name": "Mary Major",
               "email": "mary_major@example.com"
           },
           "author": {
               "date": "1484167798 -0800",
               "name": "Mary Major",
               "email": "mary_major@example.com"
           },
           "treeId": "347a3408EXAMPLE",
           "parents": [
               "4c925148EXAMPLE"
           ],
           "message": "Fix incorrect variable name"
       }
   }

1. Run the get-merge-commit command, specifying:

   • A commit specifier for the source of the merge (with the --source-commit-specifier option).

   • A commit specifier for the destination for the merge (with the --destination-commit-specifier option).

   • The merge option you want to use (with the --merge-option option).

   • The name of the repository (with the --repository-name option).

   For example, to view information about a merge commit for the source branch named bugfix-bug1234 with a destination branch named main using the THREE_WAY_MERGE strategy in a repository named MyDemoRepo:

   aws codecommit get-merge-commit --source-commit-specifier bugfix-bug1234 --destination-commit-specifier main --merge-option THREE_WAY_MERGE --repository-name MyDemoRepo

2. If successful, the output of this command returns information similar to the following:

   {
       "sourceCommitId": "c5709475EXAMPLE", 
       "destinationCommitId": "317f8570EXAMPLE", 
       "baseCommitId": "fb12a539EXAMPLE",
       "mergeCommitId": "ffc4d608eEXAMPLE"
   }

1. Run the batch-get-commits command, specifying:

   • The name of the CodeCommit repository (with the --repository-name option).

   • A list of full commit IDs for every commit about which you want to view information.

   For example, to view information about commits with the IDs 317f8570EXAMPLE and 4c925148EXAMPLE in a CodeCommit repository named MyDemoRepo:

   aws codecommit batch-get-commits  --repository-name MyDemoRepo  --commit-ids 317f8570EXAMPLE 4c925148EXAMPLE

2. If successful, the output of this command includes the following:

   • Information about the authors of the commits (as configured in Git), including the date in timestamp format and the coordinated universal time (UTC) offset.

   • Information about the committers (as configured in Git) including the date in timestamp format and the UTC offset.

   • The IDs of the Git tree where the commit exists.

   • The commit IDs of the parent commit.

   • The commit messages.

   Here is some example output, based on the preceding example command:

   {
       "commits": [
         {
           "additionalData": "",
           "committer": {
               "date": "1508280564 -0800",
               "name": "Mary Major",
               "email": "mary_major@example.com"
           },
           "author": {
               "date": "1508280564 -0800",
               "name": "Mary Major",
               "email": "mary_major@example.com"
           },
           "commitId": "317f8570EXAMPLE",
           "treeId": "1f330709EXAMPLE",
           "parents": [
               "6e147360EXAMPLE"
           ],
           "message": "Change variable name and add new response element"
       },
       {
           "additionalData": "",
           "committer": {
               "date": "1508280542 -0800",
               "name": "Li Juan",
               "email": "li_juan@example.com"
           },
           "author": {
               "date": "1508280542 -0800",
               "name": "Li Juan",
               "email": "li_juan@example.com"
           },
           "commitId": "4c925148EXAMPLE",
           "treeId": "1f330709EXAMPLE",
           "parents": [
               "317f8570EXAMPLE"
           ],
           "message": "Added new class"
       }   
   }

1. Run the aws codecommit get-differences command, specifying:

   • The name of the CodeCommit repository (with the --repository-name option).

   • The commit specifiers you want to get information about. Only --after-commit-specifier is required. If you do not specify --before-commit-specifier, all files current as of the --after-commit-specifier are shown.

   For example, to view information about the differences between commits with the IDs 317f8570EXAMPLE and 4c925148EXAMPLE in a CodeCommit repository named MyDemoRepo:

   aws codecommit get-differences  --repository-name MyDemoRepo  --before-commit-specifier 317f8570EXAMPLE --after-commit-specifier 4c925148EXAMPLE

2. If successful, the output of this command includes the following:

   • A list of differences, including the change type (A for added, D for deleted, or M for modified).

   • The mode of the file change type.

   • The ID of the Git blob object that contains the change.

   Here is some example output, based on the preceding example command:

   {
       "differences": [
           {
               "afterBlob": {
                   "path": "blob.txt",
                   "blobId": "2eb4af3bEXAMPLE",
                   "mode": "100644"
               },
               "changeType": "M",
               "beforeBlob": {
                   "path": "blob.txt",
                   "blobId": "bf7fcf28fEXAMPLE",
                   "mode": "100644"
               }
           }
       ]
   }

1. Run the aws codecommit get-blob command, specifying:

   • The name of the CodeCommit repository (with the --repository-name option).

   • The ID of the Git blob (with the --blob-id option).

   For example, to view information about a Git blob with the ID of 2eb4af3bEXAMPLE in a CodeCommit repository named MyDemoRepo:

   aws codecommit get-blob  --repository-name MyDemoRepo  --blob-id 2eb4af3bEXAMPLE

2. If successful, the output of this command includes the following:

   • The base64-encoded content of the blob, usually a file.

   For example, the output of the previous command might be similar to the following:

   {
       "content": "QSBCaW5hcnkgTGFyToEXAMPLE="
   }