Frequently Asked Questions

General

What is Tidra?

Tidra automates code changes across multiple repositories using AI. You describe what needs to change, Tidra generates the code, and you review before PRs are created.

How is Tidra different from other tools?

vs. GitHub Copilot: Copilot helps you write code in your editor. Tidra orchestrates changes across many repos at once.
vs. Find-and-replace tools: Tidra understands code context and generates appropriate changes, not just text replacement.
vs. Renovate/Dependabot: Those are great for dependency bumps. Tidra handles any code change (configs, API migrations, refactoring, etc.).

Do I need to know how to code?

Basic understanding of code helps, but Tidra makes it easier to coordinate large-scale changes. You describe what needs to happen in plain language.

Getting Started

How do I connect my repositories?

Connect your GitHub or GitLab account with a Personal Access Token. See: GitHub Integration | GitLab Integration

Can I try Tidra without risking my production repos?

Yes! Start with test repositories or create a test organization to experiment safely.

How long does setup take?

Connect Git provider: 5 minutes
First initiative: 30 minutes
Total: ~35 minutes to be productive

Initiatives

How many repositories can I update at once?

You can select as many as you want, but we recommend:

First initiative: 5-10 repos (test)
Later: 50-100 repos (typical)
Large: 100+ repos (after you're comfortable)

How long does code generation take?

Small (5-10 repos): 5-10 minutes
Medium (20-50 repos): 10-15 minutes
Large (100+ repos): 15-20 minutes

Generation happens in parallel, so adding more repos doesn't add much time.

Can I update an initiative after creating PRs?

Yes, you can regenerate changes which will update the existing PRs.

What if Tidra gets something wrong?

Review the changes before creating PRs. If something isn't right, refine your description and regenerate. You always review before PRs are created.

Can I pause an initiative?

You can cancel an initiative, which stops it and closes open PRs.

Pull Requests

Does Tidra automatically merge PRs?

No. PRs go through your normal review process. Your team reviews, approves, and merges them.

Can I customize PR descriptions?

Currently, PR descriptions are generated automatically. You can edit them in GitHub/GitLab after creation.

What if a PR is rejected?

That's fine. The initiative continues for other repos. You can address rejected PRs individually or create a new initiative with updated changes.

How do I track PR progress?

The initiative dashboard shows real-time status of all PRs: open, merged, blocked, etc.

Technical

Which Git providers do you support?

GitHub (github.com)
GitLab (gitlab.com and self-managed)

More providers coming soon.

Which programming languages work?

Tidra works with any text-based code:

Python, JavaScript, TypeScript, Go, Ruby, Java, C#, etc.
Configuration files (YAML, JSON, TOML, etc.)
Infrastructure as Code (Terraform, CloudFormation, etc.)
Documentation (Markdown, etc.)

Can Tidra access private repositories?

Yes, if your Personal Access Token has the appropriate permissions.

Does Tidra store my code?

Tidra reads your code to generate changes but doesn't permanently store it. Code is processed in secure, isolated environments and deleted after the initiative completes.

Can Tidra run my tests?

Not automatically. You run tests as part of your normal PR review process.

Security & Privacy

Is my code secure?

Yes. Code is processed in isolated, secure environments with encryption in transit and at rest. See our Security Policy.

Who can see my initiatives?

Only people in your organization who have access to Tidra.

Can I delete my data?

Yes. You can delete your account and all data from Settings.

Do you have SOC 2 / ISO 27001?

Billing & Plans

How much does Tidra cost?

Pricing varies by plan. Contact sales for details.

Is there a free trial?

How is usage measured?

Typically by number of initiatives or repositories processed. Exact metrics depend on your plan.

Best Practices

What makes a good first initiative?

Simple, well-defined change
5-10 repositories
Easy to validate by looking at code
Not mission-critical

Examples: Add a file, update a config value, add documentation section.

How specific should my description be?

Very specific. Include:

What to change
Where to find it
What it should become
Examples (before/after)

The more detail, the better.

How many repositories should I start with?

Start with 5-10 repos to validate quality. Then scale up to 50+ once comfortable.

Should I create PRs all at once?

For large initiatives (50+ repos), consider creating PRs in batches (20-30 at a time) to avoid overwhelming reviewers.

Troubleshooting

Why aren't my PRs being created?

Common reasons:

No write permission to repos
Branch protection rules blocking
Network issues

See Troubleshooting for solutions.

Why is code quality poor?

Usually means description needs more detail. Add examples and be more explicit. Test on 3-5 repos first, then refine.

Some repos failed - why?

Different repos have different structures. Add guidance for edge cases in your description, or skip those repos and handle manually.

Support

How do I get help?

Email: [email protected]
Documentation: docs.tidra.com

What's your response time?

Usually within 24 hours for support requests.

Next Steps

Getting Started - Begin using Tidra
Use Cases - See examples
Best Practices - Tips for success
Support - Get help