Connecting Repositories

FlagShark monitors your GitHub repositories for feature flag activity. This guide covers how to connect new repositories, configure monitoring settings, and manage existing connections.

Adding Repositories

During Initial Setup

When you first install FlagShark, you'll choose which repositories to monitor:

1. All repositories - Automatically monitors all current and future repos
2. Select repositories - Choose specific repos to monitor

Adding Repositories Later

To add more repositories after initial setup:

1. Go to Settings → Repositories in the FlagShark dashboard
2. Click "Add Repositories"
3. Select the repositories you want to add
4. Click "Save"

If you don't see a repository you expect:

• Ensure the FlagShark GitHub App has access (check GitHub App settings)
• Verify you have admin access to the repository
• The repository must be in an organization or account where FlagShark is installed

Repository Settings

Each repository can have individual settings that override workspace defaults.

Detection Settings

Configure how FlagShark detects flags in each repository:

Custom Configuration

For repository-specific flag patterns, create a .flagshark.yaml file in the repository root. See Configuration for details.

Repository Status

Each repository shows its current status in the dashboard:

Scanning Existing Code

When you track a repository, FlagShark automatically scans the existing code for feature flags.

Automatic Initial Scan

When you enable tracking for a repository:

You can track the scan progress in real-time via the dashboard.

Manual Re-scans

You can also trigger a manual scan at any time:

1. Go to the repository page in the FlagShark dashboard
2. Click "Scan Repository"
3. Wait for the scan to complete (typically 1-5 minutes depending on repo size)

Manual scans are useful if you:

• Want to re-sync your flag inventory
• Suspect some flags weren't detected
• Added FlagShark after significant codebase changes

The scan will:

• Analyze all files in the default branch
• Detect existing feature flags
• Update your flag inventory

Scan Limitations

• Scans only analyze the default branch
• Historical flag additions/removals won't have associated PRs
• Large repositories (>10,000 files) may take longer

Working with Monorepos

FlagShark supports monorepo architectures. For large monorepos:

Path-Based Filtering

Configure which paths to monitor in your .flagshark.yaml:

# Only scan specific directories
include_paths:
  - "packages/web/**"
  - "packages/api/**"

# Exclude paths
exclude_paths:
  - "packages/legacy/**"
  - "**/test/**"

Team Ownership

Map paths to teams for better organization:

ownership:
  - paths: ["packages/checkout/**"]
    team: "payments"
  - paths: ["packages/auth/**"]
    team: "identity"

Removing Repositories

To stop monitoring a repository:

From FlagShark

1. Go to Settings → Repositories
2. Find the repository
3. Click the menu (⋮) → Remove

This removes the repository from FlagShark but keeps the GitHub App installed.

From GitHub

1. Go to GitHub → Settings → Applications → FlagShark
2. Click Configure
3. Deselect the repository

This removes FlagShark's access to the repository entirely.

Troubleshooting

Repository Not Appearing

If a repository doesn't appear in FlagShark:

1. Check GitHub App installation - Verify FlagShark has access in GitHub settings
2. Verify permissions - You need admin access to add repositories
3. Check organization settings - Some orgs require approval for new app installations

Webhooks Not Firing

If FlagShark isn't detecting PRs:

1. Check repository status - Look for "Error" status in the dashboard
2. Verify webhook delivery - Check GitHub webhook settings for delivery failures
3. Test with a new PR - Create a simple test PR to trigger detection

See Troubleshooting for more solutions.

Next Steps

• Configure flag detection for custom flag patterns
• Enable branch protection for better tracking
• Set up team workflows for larger teams