#!/usr/bin/env node
/**
 * GitHub Feature Sync CLI
 *
 * CLI wrapper for GitHubFeatureSync.syncFeatureToGitHub()
 * Called by post-increment-planning.sh hook to create GitHub issues
 * after increment creation.
 *
 * Usage:
 *   node github-feature-sync-cli.js <feature-id>
 *   node github-feature-sync-cli.js FS-062
 *
 * Environment:
 *   GITHUB_TOKEN - Required
 *   GITHUB_OWNER - Optional (detected from config.json or git remote)
 *   GITHUB_REPO  - Optional (detected from config.json or git remote)
 *
 * @see ADR-0139 (Unified Post-Increment Sync)
 */
/**
 * Resolve GitHub config (owner/repo) with a single canonical precedence order.
 *
 * Resolution order (documented for both CLI and hooks):
 * 1. CLI flags / env vars: GITHUB_OWNER, GITHUB_REPO
 * 2. .specweave/config.json — sync.github.owner/repo
 * 3. .specweave/config.json — multiProject.projects[active].externalTools.github
 * 4. .specweave/config.json — sync.profiles[defaultProfile].config
 * 5. .specweave/config.json — first GitHub profile (fallback)
 * 6. Git remote detection (git remote get-url origin)
 *
 * This is the SINGLE source of truth for owner/repo config.
 * Shell hooks should read the same config.json paths in the same order.
 */
export declare function resolveGitHubConfig(options?: {
    cliOwner?: string;
    cliRepo?: string;
    cliToken?: string;
    projectRoot?: string;
}): Promise<{
    owner: string;
    repo: string;
    token: string;
} | null>;
//# sourceMappingURL=github-feature-sync-cli.d.ts.map