Best Practices

Source Provider Best Practices

Standardize GitHub, GitLab, Azure DevOps, Bitbucket, and AWS CodeBuild setup so DevLyTicks can turn repository, review, issue, build, and deployment activity into reliable engineering analytics.

Provider Coverage

GitHub

Repositories, commits, pull requests, issues, branches, releases, Actions, builds, and deployments.

Use GitHub OAuth or an organization token with access to the repositories you want to track.

GitLab

Repositories, commits, merge requests, issues, CI pipelines, builds, and deployments.

Connect an active GitLab source provider account, then track repositories from provider discovery.

Azure DevOps

Repositories, commits, pull requests, work items, Azure Pipelines runs, builds, and release deployments.

Use an Azure DevOps account scoped to the organization and project collections DevLyTicks should ingest.

Bitbucket

Repositories, commits, pull requests, issues, Pipelines runs, builds, and deployments.

Connect a Bitbucket account with repository read access, then select repositories from discovery.

AWS CodeBuild

Build project discovery, repository mapping, historical build ingestion, and live build webhooks.

Connect an AWS access key pair, map each CodeBuild project to a tracked repository, then enable webhooks for live events.

Workflow Practices

Use consistent repository names and namespaces across source providers so teams can recognize the same service in analytics, webhooks, and reports.
Keep default branches accurate. DevLyTicks uses them when calculating activity, repository health, and delivery trends.
Prefer pull request or merge request workflows with explicit reviewers, labels, and linked work items where your provider supports them.
Create releases, tags, pipeline deployments, or webhooks for production delivery events so DORA metrics have clear deployment evidence.
Map CI/CD projects to tracked repositories when the build system is separate from the source provider, especially for AWS CodeBuild.

Credential Practices

Create provider credentials at the organization level instead of personal one-off tokens when possible.
Grant read access only to repositories and projects that should appear in DevLyTicks.
Rotate provider credentials on the same cadence as other engineering secrets.
Keep at least one DevLyTicks admin who can reconnect provider accounts if the original token owner leaves the organization.

Back to Documentation

Best Practices

Source Provider Best Practices

Standardize GitHub, GitLab, Azure DevOps, Bitbucket, and AWS CodeBuild setup so DevLyTicks can turn repository, review, issue, build, and deployment activity into reliable engineering analytics.

Provider Coverage

GitHub

Repositories, commits, pull requests, issues, branches, releases, Actions, builds, and deployments.

Use GitHub OAuth or an organization token with access to the repositories you want to track.

GitLab

Repositories, commits, merge requests, issues, CI pipelines, builds, and deployments.

Connect an active GitLab source provider account, then track repositories from provider discovery.

Azure DevOps

Repositories, commits, pull requests, work items, Azure Pipelines runs, builds, and release deployments.

Use an Azure DevOps account scoped to the organization and project collections DevLyTicks should ingest.

Bitbucket

Repositories, commits, pull requests, issues, Pipelines runs, builds, and deployments.

Connect a Bitbucket account with repository read access, then select repositories from discovery.

AWS CodeBuild

Build project discovery, repository mapping, historical build ingestion, and live build webhooks.

Connect an AWS access key pair, map each CodeBuild project to a tracked repository, then enable webhooks for live events.

Workflow Practices

Use consistent repository names and namespaces across source providers so teams can recognize the same service in analytics, webhooks, and reports.
Keep default branches accurate. DevLyTicks uses them when calculating activity, repository health, and delivery trends.
Prefer pull request or merge request workflows with explicit reviewers, labels, and linked work items where your provider supports them.
Create releases, tags, pipeline deployments, or webhooks for production delivery events so DORA metrics have clear deployment evidence.
Map CI/CD projects to tracked repositories when the build system is separate from the source provider, especially for AWS CodeBuild.

Credential Practices

Create provider credentials at the organization level instead of personal one-off tokens when possible.
Grant read access only to repositories and projects that should appear in DevLyTicks.
Rotate provider credentials on the same cadence as other engineering secrets.
Keep at least one DevLyTicks admin who can reconnect provider accounts if the original token owner leaves the organization.