LaunchDarkly Code References: Backend

Wire up the LaunchDarkly `find-code-references` GitHub Action in every backend
repo that uses the LaunchDarkly SDK.

For each repository:
1. Detect LaunchDarkly SDK usage in backend code:
   - Go: `gopkg.in/launchdarkly/go-server-sdk.v5` or `launchdarkly/go-server-sdk/v7`
   - Java: `com.launchdarkly:launchdarkly-java-server-sdk`
   - Python: `launchdarkly-server-sdk`
   - Ruby: `launchdarkly-server-sdk` gem
   - .NET: `LaunchDarkly.ServerSdk`
   Skip the repo if no LaunchDarkly SDK is found.
2. Create `.github/workflows/launchdarkly-code-references.yml`:
   - Triggers on `push` to `main` and on a weekly cron (`'0 6 * * 1'`)
   - Uses `actions/checkout@v4` with `fetch-depth: 0`
   - Uses `launchdarkly/find-code-references@v2`
   - Passes `accessToken: ${{ secrets.LD_ACCESS_TOKEN }}`
   - Sets `projKey` from the per-team mapping (CSV provided separately).
     If the repo is not in the mapping, use `TODO-ld-project-key` and flag for review.
3. Skip repos that already have the workflow installed.

In the PR body, document the required `LD_ACCESS_TOKEN` repository or organization
secret so platform teams can provision it.

The Problem

LaunchDarkly’s Code References feature shows you which files and lines reference each flag, invaluable when cleaning up stale flags or auditing impact. But it only works if every repo has the find-code-references Action wired up, scheduled, and pointed at the correct project.

Doing this manually means visiting every backend repo, adding a workflow, configuring a project key, and provisioning an access token secret. Multiply by hundreds of repos and the work never gets prioritized.

What Tidra Does

1. Identifies backend repos (Go, Java, Python, Ruby, .NET) that use the LaunchDarkly SDK
2. Adds .github/workflows/launchdarkly-code-references.yml configured to run on push to main and weekly
3. Sets the LaunchDarkly project key based on a per-team mapping you provide
4. Documents the required LD_ACCESS_TOKEN secret in the PR body so platform teams can provision it
5. Skips repos that already have the workflow installed

Before & After

Customization Tips

• Project key mapping: Provide a CSV mapping repo name → LaunchDarkly project key so Tidra can fill it in per-repo.
• Token provisioning: Tidra documents the required secret but does not provision it. Pair with a secret-rollout tool.
• Frontend repos: For frontend repos, swap aliases for JSX/TSX-aware patterns and consider a separate initiative.