Amazon CodeCommit is no longer available to new customers. Existing customers of
Amazon CodeCommit can continue to use the service as normal.
Learn more"
Troubleshooting Amazon CodeCommit
The following information might help you troubleshoot common issues in Amazon CodeCommit.
Topics
- Troubleshooting Git credentials and HTTPS connections to Amazon CodeCommit
- Troubleshooting git-remote-codecommit and Amazon CodeCommit
- Troubleshooting SSH connections to Amazon CodeCommit
- Troubleshooting the credential helper and HTTPS connections to Amazon CodeCommit
- Troubleshooting Git clients and Amazon CodeCommit
- Troubleshooting access errors and Amazon CodeCommit
- Troubleshooting configuration errors and Amazon CodeCommit
- Troubleshooting console errors and Amazon CodeCommit
- Troubleshooting triggers and Amazon CodeCommit
- Turn on debugging
Turn on debugging
Problem: I want to turn on debugging to get more information about my repository and how Git is executing commands.
Possible fixes: Try the following:
-
At the terminal or command prompt, run the following commands on your local machine before running Git commands:
On Linux, OS X, or Unix:
export GIT_TRACE_PACKET=1 export GIT_TRACE=1 export GIT_CURL_VERBOSE=1
On Windows:
set GIT_TRACE_PACKET=1 set GIT_TRACE=1 set GIT_CURL_VERBOSE=1
Note
Setting
GIT_CURL_VERBOSE
is useful for HTTPS connections only. SSH does not use thelibcurl
library. -
To get more information about your Git repository, we recommend installing the latest version of git-sizer
. Follow the instructions for intalling the utility appropriate to your operating system and environment. Once installed, at the command line or terminal, change directories to your local repository and then run the following command: git-sizer --verbose
Tip
Consider saving the output of the command to a file so that you can easily share it with others when troubleshooting problems, particularly over time.