Integrate Git-based repositories with your other software delivery tools
When dealing with millions of lines of code, it’s very important to know why the code was written in the first place. For safety-critical or highly regulated products, it is absolutely essential. However, manually linking code changes to the originating feature or defect is both tedious and error prone.
Why Integrate Git?
Software delivery organizations integrate their Git-based repositories, which provide source code version control, and the other tools that house the originating requirements, stories, defects and tests.
Thanks to integration, developers can automate code traceability and link lines of source code they changed to the originating artifact (requirement, user story, defect or task).
Popular Git Integrations
Code traceability is implemented in one of two ways. In the first, upon ‘code commit’, an existing artifact is updated with a link to the changeset. In the second, upon ‘code commit’, a new artifact for the changeset is created and linked to an existing artifact (requirement, user story, defect or task).
Tasktop supports both these flavors of code traceability between Git-based repositories - GitHub, GitLab, BitBucket, Gerrit, Gitea and Azure Repos - and tens of popular tools in the software delivery toolchain, like Jira, Azure DevOps, Jama, ServiceNow and VersionOne.
To see everything Git-based repositories can integrate with through Tasktop, visit our full list of supported tools.
Want to see how Tasktop integrates Git-based repositories?