You can use Cloud Source Repositories for collaborative development of any application or service, including those that run on App Engine and Compute Engine. If you are using Stackdriver Debugger, you can use Cloud Source Repositories and related tools in the GCP Console to view debugging information alongside your code during application runtime.
Using Cloud Source Repositories is easy if you are familiar with Git. For
example, you can add Cloud Source Repositories to a local Git repository as a
remote, or you can connect it to a hosted repository on GitHub or Bitbucket.
From a local repository, you can use the standard set of Git commands to
interact with the repository in the cloud, including
You can create multiple repositories for a single Cloud Platform project, allowing you to organize the code associated with your cloud project in whatever way works best for you.
Because repositories in Cloud Source Repositories are Git repositories, you can continue to use the editor of your choice to work on your code. For a more integrated experience, see the following topics:
Cloud Source Repositories also provide a source browser that you can use to view repository files from within the GCP Console.
Automatic Stackdriver logging
Cloud Source Repositories automatically sends logs to Stackdriver Logging to help data access tracking and troubleshooting.
By logging activity on repositories, you can review logs of recent repository synchronization activity, administrative actions such as creations, deletions, and permission changes, and repository access by other users. Moreover, you can configure notification settings such that an alert is sent to you when an error is logged during a repository synchronization.
For more information regarding reading and writing log entries in Stackdriver Logging as well as possible billing configurations to manage storage of your logs and avoid incurring overage charges, see this quickstart.
Security key detection
Cloud Source Repositories gives you the option to use security key detection to
git push transactions that contain sensitive information. This
feature is designed to improve the security of your source code. Enabling it
is a best practice. For more
information, see Detecting Security Keys