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

Managing Initiatives

Learn how to track, organize, and manage your initiatives.

The Initiative Dashboard

Your main view for all initiatives shows:

Initiative list:

  • Name and status (Active, Done, Cancelled)
  • Number of repositories
  • Progress percentage
  • When created and last updated
  • Owner

Initiative Details

Click any initiative to see:

Status Summary

Visual breakdown of all repositories:

  • Pending: PRs not yet created
  • In Progress: PRs open and awaiting review
  • Completed: PRs merged
  • Blocked: PRs needing attention
  • Not Started: Changes not yet generated

Repository List

All repositories in the initiative with:

  • Repository name
  • Status
  • PR link (if created)
  • PR Status
  • Complexity (Low/Medium/High)
  • Last updated

Click a repository to see:

  • Code diff (what changed)
  • Code Change Summary
  • PR Settings
  • Comments and reviews

Code Complexity

Breakdown by complexity level:

  • Low: Simple changes, quick to review
  • Medium: Moderate changes, needs careful review
  • High: Complex changes, thorough review needed

Use this to prioritize reviews.

Time Savings

Estimated time saved:

  • Total hours saved
  • Hours per repository
  • Based on manual effort vs. Tidra

Initiative Actions

While Active

Regenerate changes: If you need to update the code after PRs are created, you can regenerate (this will update existing PRs).

Add repositories: Add more repos to an existing initiative.

Cancel initiative: Stop the initiative and close all open PRs.

When Complete

Mark as Done: Once all PRs are merged or closed, mark the initiative as done.

Working with Pull Requests

PR Status

Each PR can be:

  • Draft: Pending
  • Open: Awaiting review
  • Merged: Successfully merged
  • Closed: Closed without merging

Tracking Reviews

The dashboard shows:

  • Which PRs need review
  • Which are approved
  • Which have requested changes
  • Which are blocked

Handling Rejected PRs

If a PR is closed without merging:

  1. Click the repository to see why
  2. Decide if changes are needed
  3. Either:
    • Regenerate with updated description
    • Accept that this repo doesn't need the change
    • Make manual changes if needed

The rest of the initiative continues regardless.

Organizing Initiatives

Naming Conventions

Use consistent naming:

  • [Team] - [What] - [Quarter]
  • Example: "Platform - Node 20 Migration - Q1 2026"

Or:

  • [Type] - [Description]
  • Example: "Security - Add SECURITY.md files"

Grouping

Group related initiatives:

  • Use consistent prefixes
  • Tag by team or project
  • Track by quarter or sprint

Best Practices

Regular Check-ins

Check your active initiatives:

  • Daily: Quick status check
  • Weekly: Detailed review, unblock issues
  • Monthly: Archive completed initiatives

Keep Dashboard Clean

  • Mark initiatives as Done when complete
  • Cancel initiatives that are no longer needed

Track Metrics

Monitor:

  • Completion rates (goal: 80%+)
  • Time to merge (track trends)
  • Time saved (celebrate wins)

Troubleshooting

Initiative Stuck

If an initiative isn't progressing:

  1. Check PR status - are they blocked?
  2. Check with reviewers - do they need context?
  3. Check code quality - do PRs need changes?

Low Merge Rate

If fewer than 50% of PRs are merging:

  1. Review code quality
  2. Refine description and regenerate
  3. Test with fewer repos first

PRs Taking Too Long

If PRs sit unreviewed:

  1. Add to team's review queue
  2. Notify reviewers via Slack
  3. Set expectations upfront next time

Next Steps

Updated about 3 hours ago