DevDynamics
  • Overview
    • 💡Getting Started
    • ❓FAQ
    • Configuration
      • Best Practices
      • Setting Up Issue Management System in DevDynamics
      • Setting Up Version Control
      • Setting Up Investment Categories in DevDynamics
      • Configuring Communication Channels in DevDynamics
      • Change Failure
      • Deployment
      • Manage Contributors
      • Manage Teams
  • Integrations
    • GitLab
    • GitHub
    • BitBucket
    • On-Premises BitBucket
    • On-Premises GitHub
    • Jira
    • Slack
    • Linear
    • Pagerduty
    • Microsoft Teams
    • Sonar Cloud
    • Sonar Qube
    • CI/CD
    • Azure Repo
    • Azure Board
    • Opsgenie
    • ClickUp
    • Outlook
    • Google Calendar
    • Shortcut
    • OpenProject
    • Asana
    • Test Suite
  • Installations
    • On-Premises Agent Installation Guide
  • Features
    • Metrics
      • Cycle Time Metrics
      • DORA Metrics
      • Git Dashboard
        • Feedback Responsiveness Index (FRI)
        • Review Responsiveness Index (RRI)
        • Review Completion Index (RCI)
        • Reviewer Distribution
        • Average Active Days
        • PR Review Health
        • Open PR Age
        • Work Breakdown: Distribution of Work (Lines of Code)
      • Ticket Dashboard
        • Issue Throughput
        • Open Issue Age
        • Backward Momentum
        • Issue Cycle Time Spread
        • Requirement Stability Index
      • Issue Closed Count/Task Velocity
      • Story Points Completed
      • Bug Closed Count
      • Bug Opened Count
      • Pull Request Merged Count
      • PR Comment Count
      • Pull Request Size
      • Pull Request Open Count
      • Pull Request Review Count
      • Contributors Working on Non-Working Days
      • Contributors working out of office hours
      • Contributors getting burnout
    • Team Insights
    • Initiatives
Powered by GitBook
On this page
  1. Overview
  2. Configuration

Setting Up Version Control

Step-by-Step Guide to Setting Up Version Control Integrations in DevDynamics

PreviousSetting Up Issue Management System in DevDynamicsNextSetting Up Investment Categories in DevDynamics

Last updated 11 months ago

This guide will help you set up your version control integrations and configure them to measure all the metrics and insights generated by DevDynamics. We'll demonstrate the setup using GitHub, but the process is similar for other version control tools.

Step 1: Integrate Your Version Control System

  • Available Integrations: DevDynamics supports various version control tools, including: GitHub, GitLab, Azure Repos,Bitbucket, Custom Tools (configurable as needed)

  • Integration Process:

  • Integrate your version control system during onboarding.

  • After integration, you will see an Active Status on your screen. This indicates that DevDynamics is successfully pulling data from your version control system.

  • DevDynamics pulls data using APIs, only storing metadata and not copying your repositories.

Step 2: Configure Repositories

  • View Repository List:

  • You will see a list of all repositories in your version control system, with two main columns:

  • Active: A switch button to enable or disable tracking for specific repositories.

  • Settings: Additional configuration options for each repository.

  • Enable/Disable Tracking:

  • Use the switch button in the Active column to enable or disable tracking for specific repositories.

Step 3: Exclude Data

Excluding branch or PRs helps you focus on relevant data and avoid noise in your metrics.

  • Exclude branch - If your team work with feature branches you should add branches that are not a target to a direct commit and used only as a baseline branch (e.g. master, main, stage,dev )

  • Exclude Pull Request by title or Label - Certain open PR's affect your cycle time. If those PR does not represent the feature or bug change you can exclude them by title or label.

By following these steps, you can effectively set up and configure version control integrations in DevDynamics. This setup ensures that your version control data is accurately tracked and that any unnecessary data is excluded from your metrics, providing you with precise insights and measurements. This helps maintain a clean and relevant dataset for better analysis and decision-making.

\