Abstract: A system and method for backing out changes via a version control system. One or more changes are made by a developer and committed to a first branch of a repository of the version control system. While validating the changes during a software build, at least one error occurs as a result of the developer's changes. In response to the error, the changes are automatically reverted so that the changes are backed out from the first branch thereby defining a first reversion. A second branch is automatically created in the repository with the first reversion pulled from the first branch without the changes. Then, in response to the error, the changes are automatically reapplied to the first reversion of the second branch of the repository.

Abstract: Centralized tracking and management of coding time in a distributed source control system environment for determining software development agility is provided. A centralized coding time tracking and management (CCTTM) tool is provided that gathers file edit data from developers' machines, collects file commit data associated with changes pushed to a centralized server, aggregates the collected data into a merged table, analyzes the aggregated data, and generates reports that indicate a level of agility of a company's I2D pipeline.

Abstract: Synchronizing a code base between source control systems is provided. A synchronization engine provides: forward bridging, where source code is migrated from a first source control system to a second source control system; pull bridging, where source code is migrated from the second source control system to the first source control system; and reverse bridging, where source code is merged from the second source control system to the main branch of source code in the first source control system.