Guides
v1.0
Guides
Start typing to search…
  1. Introduction

Use Cases

Tidra works for any repetitive code change across multiple repositories. Here are the most common patterns.

Configuration Standardization

What it is: Ensuring all repos have consistent configuration files

Examples:

  • Standardize CI/CD pipeline configurations
  • Add security scanning configs
  • Update Docker base images
  • Standardize build scripts
  • Add required documentation files

Why it matters:

  • Security compliance
  • Consistent developer experience
  • Enable automation
  • Reduce technical debt

Tidra approach:

"Add Snyk security scanning step to all GitHub Actions workflows. Add it after the build step, using the org's Snyk token from GitHub secrets."

Time saved: Manual: 4-6 weeks | With Tidra: 3-4 days

CI/CD Pipeline Updates

What it is: Updating build and deployment pipelines

Examples:

  • Migrate GitHub Actions from Node 16 to Node 20
  • Update runner images
  • Add new pipeline steps (security scanning, linting)
  • Change deployment targets
  • Update secret references

Why it matters:

  • Stay current with deprecations
  • Add security/compliance steps
  • Improve build performance
  • Standardize across teams

Tidra approach:

"Update all GitHub Actions workflows to use actions/setup-node@v4 with node-version: 20"

Time saved: Manual: 3-4 weeks | With Tidra: 3-4 days

API Migrations

What it is: Updating code when APIs change

Examples:

  • Migrate from deprecated endpoints to new ones
  • Update authentication methods
  • Change request/response formats
  • Replace removed methods
  • Update client library versions

Why it matters:

  • APIs get deprecated with deadlines
  • Breaking changes require coordination
  • Old APIs may have security issues
  • Performance improvements in new APIs

Tidra approach:

"Replace all calls to api.old.com with api.new.com and update the authentication header from X-API-Key to Authorization: Bearer"

Time saved: Manual: 4-6 weeks | With Tidra: 1 week

Dependency Updates

What it is: Updating package versions across repos

Examples:

  • Update internal shared libraries
  • Bump framework versions
  • Update language versions (Python 3.9 → 3.10)
  • Replace deprecated packages
  • Security patches for vulnerable dependencies

Why it matters:

  • Security vulnerabilities
  • Access new features
  • Stay supported
  • Technical debt reduction

Tidra approach:

"Update @company/shared-utils from version 2.x to 3.x in package.json. Update import statements to use the new module paths."

Time saved: Manual: 2-4 weeks | With Tidra: 1 week

Note: Works best when you don't have complex private dependency setups.

Security & Compliance

What it is: Rolling out security improvements or meeting compliance requirements

Examples:

  • Add security.md vulnerability disclosure policies
  • Implement input validation patterns
  • Add security headers to API responses
  • Update encryption methods
  • Add audit logging

Why it matters:

  • Compliance deadlines (SOC 2, ISO, etc.)
  • Security incidents require fast response
  • Regulatory requirements
  • Risk reduction

Tidra approach:

"Add a SECURITY.md file to all repositories with our vulnerability disclosure policy and contact information"

Time saved: Manual: 2-3 weeks | With Tidra: 2-3 days

Documentation Updates

What it is: Adding or updating documentation files

Examples:

  • Add README sections
  • Update contributor guidelines
  • Add architecture decision records (ADRs)
  • Standardize code comments
  • Update copyright notices

Why it matters:

  • Onboarding new developers
  • Compliance requirements
  • Knowledge preservation
  • Team efficiency

Tidra approach:

"Add a 'Local Development' section to all README files with instructions for running the service locally"

Time saved: Manual: 1-2 weeks | With Tidra: 1-2 days

Code Quality Improvements

What it is: Improving code patterns and practices

Examples:

  • Add error handling to API calls
  • Implement consistent logging
  • Update code style
  • Add type hints (Python, TypeScript)
  • Replace deprecated language features

Why it matters:

  • Reduce bugs
  • Improve maintainability
  • Easier debugging
  • Better developer experience

Tidra approach:

"Add error handling to all HTTP requests using the requests library. Wrap in try/except and log errors with our standard logger."

Time saved: Manual: 4-8 weeks | With Tidra: 1-2 weeks

Infrastructure as Code

What it is: Updating infrastructure definitions

Examples:

  • Update Terraform provider versions
  • Change resource configurations
  • Add tags/labels to resources
  • Update Kubernetes manifests
  • Change CloudFormation parameters

Why it matters:

  • Stay current with provider changes
  • Cost optimization
  • Security improvements
  • Compliance tagging

Tidra approach:

"Update all Terraform files to use AWS provider version 5.x and update the required_version to >= 1.5"

Time saved: Manual: 2-4 weeks | With Tidra: 3-5 days

Framework Upgrades

What it is: Migrating to new framework versions

Examples:

  • React 17 → 18
  • Django 3 → 4
  • Rails 6 → 7
  • .NET 6 → 8

Why it matters:

  • Security patches
  • Performance improvements
  • New features
  • End of support deadlines

Tidra approach:

"Update React from 17.x to 18.x in package.json. Update ReactDOM.render to use createRoot as per React 18 migration guide."

Time saved: Manual: 6-12 weeks | With Tidra: 2-3 weeks

Getting Started

Popular first initiatives:

  • Configuration standardization
  • CI/CD pipeline updates
  • Documentation updates

More complex initiatives:

  • API migrations
  • Framework upgrades
  • Code quality improvements

Start with what matters most to your organization, and validate quality with a small set of repos before scaling up.

Next Steps


Updated about 3 hours ago