In the context of Developing in the Cloud and using the Guidewire Cloud Platform (GWCP), managing source code follows standard Git-based workflows integrated with Atlassian Bitbucket. For a developer to successfully share their local configuration changes with the rest of the team, they must follow a sequence that ensures code integrity and avoids " merge hell. "

The first essential step is Committing the changes locally (Option B). This records the developer ' s progress in their local repository ' s history. However, because other developers may have pushed changes to the shared repository in the meantime, the developer must synchronize their local environment. This is achieved by Pulling the latest changes from the remote repository and rebasing (Option A). Rebasing is preferred in the Guidewire curriculum because it creates a clean, linear project history by moving the developer ' s custom commits to the " tip " of the updated master or feature branch. Finally, once the local branch is current and all conflicts are resolved, the developer must Push the finished branch to the remote Bitbucket repository (Option E). Only after the code is in Bitbucket can it be picked up by TeamCity for automated building and testing.

Deploying to a planet (Option C) and creating build schedules (Option D) are downstream activities that occur after the code has been successfully merged into the shared repository. Similarly, Quality Gates (Option F) are pre-configured environment standards rather than a step in the Git commit-and-push workflow. Adhering to the commit-rebase-push cycle is the verified best practice for collaborative cloud development.