gitflow-analytics 1.0.0__py3-none-any.whl → 1.0.1__py3-none-any.whl

gitflow_analytics-1.0.1.dist-info/METADATA

@@ -0,0 +1,463 @@
+Metadata-Version: 2.4
+Name: gitflow-analytics
+Version: 1.0.1
+Summary: Analyze Git repositories for developer productivity insights
+Author-email: Bob Matyas <bobmatnyc@gmail.com>
+License: MIT
+Project-URL: Homepage, https://github.com/bobmatnyc/gitflow-analytics
+Project-URL: Documentation, https://github.com/bobmatnyc/gitflow-analytics/blob/main/README.md
+Project-URL: Repository, https://github.com/bobmatnyc/gitflow-analytics
+Project-URL: Issues, https://github.com/bobmatnyc/gitflow-analytics/issues
+Keywords: git,analytics,productivity,metrics,development
+Classifier: Development Status :: 5 - Production/Stable
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.8
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Software Development :: Version Control :: Git
+Classifier: Topic :: Software Development :: Quality Assurance
+Requires-Python: >=3.8
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: click>=8.1
+Requires-Dist: gitpython>=3.1
+Requires-Dist: tqdm>=4.65
+Requires-Dist: sqlalchemy>=2.0
+Requires-Dist: pandas>=2.0
+Requires-Dist: pyyaml>=6.0
+Requires-Dist: python-dateutil>=2.8
+Requires-Dist: python-dotenv>=1.0
+Provides-Extra: dev
+Requires-Dist: pytest>=7.0; extra == "dev"
+Requires-Dist: pytest-cov>=4.0; extra == "dev"
+Requires-Dist: pytest-mock>=3.0; extra == "dev"
+Requires-Dist: ruff>=0.1.0; extra == "dev"
+Requires-Dist: mypy>=1.0; extra == "dev"
+Requires-Dist: black>=23.0; extra == "dev"
+Provides-Extra: github
+Requires-Dist: pygithub>=1.58; extra == "github"
+Provides-Extra: all
+Requires-Dist: gitflow-analytics[github]; extra == "all"
+Dynamic: license-file
+
+# GitFlow Analytics
+
+A Python package for analyzing Git repositories to generate comprehensive developer productivity reports. It extracts data directly from Git history and GitHub APIs, providing weekly summaries, productivity insights, and gap analysis.
+
+## Features
+
+- 🚀 **Multi-repository analysis** with project grouping
+- 🏢 **Organization-based repository discovery** from GitHub
+- 👥 **Developer identity resolution** and normalization
+- 📊 **Work volume analysis** (absolute vs relative effort)
+- 🎯 **Story point extraction** from commit messages and PR descriptions
+- 🎫 **Multi-platform ticket tracking** (JIRA, GitHub Issues, ClickUp, Linear)
+- 📈 **Weekly CSV reports** with productivity metrics
+- 🔒 **Data anonymization** for external sharing
+- ⚡ **Smart caching** for fast repeated analyses
+- 🔄 **Batch processing** for large repositories
+
+## Quick Start
+
+### Installation
+
+```bash
+pip install gitflow-analytics
+```
+
+### Basic Usage
+
+1. Create a configuration file (`config.yaml`):
+
+**Option A: Organization-based (Automatic Repository Discovery)**
+```yaml
+version: "1.0"
+
+github:
+  token: "${GITHUB_TOKEN}"
+  organization: "myorg"  # Automatically discovers all repositories
+
+analysis:
+  story_point_patterns:
+    - "(?:story\\s*points?|sp|pts?)\\s*[:=]\\s*(\\d+)"
+    - "\\[(\\d+)\\s*(?:sp|pts?)\\]"
+```
+
+**Option B: Repository-based (Manual Configuration)**
+```yaml
+version: "1.0"
+
+github:
+  token: "${GITHUB_TOKEN}"
+  owner: "${GITHUB_OWNER}"
+
+repositories:
+  - name: "frontend"
+    path: "~/repos/frontend"
+    github_repo: "myorg/frontend"
+    project_key: "FRONTEND"
+    
+  - name: "backend"
+    path: "~/repos/backend"
+    github_repo: "myorg/backend"
+    project_key: "BACKEND"
+
+analysis:
+  story_point_patterns:
+    - "(?:story\\s*points?|sp|pts?)\\s*[:=]\\s*(\\d+)"
+    - "\\[(\\d+)\\s*(?:sp|pts?)\\]"
+```
+
+2. Create a `.env` file in the same directory as your `config.yaml`:
+
+```bash
+# .env
+GITHUB_TOKEN=ghp_your_github_token_here
+GITHUB_OWNER=your_github_org  # Only for repository-based setup
+```
+
+3. Run the analysis:
+
+```bash
+gitflow-analytics analyze -c config.yaml
+```
+
+## Configuration Options
+
+### Environment Variables and Credentials
+
+GitFlow Analytics automatically loads environment variables from a `.env` file in the same directory as your configuration YAML. This is the recommended approach for managing credentials securely.
+
+#### Step 1: Create a `.env` file
+
+Create a `.env` file next to your configuration YAML:
+
+```bash
+# .env file (same directory as your config.yaml)
+# GitHub credentials (required)
+GITHUB_TOKEN=ghp_xxxxxxxxxxxxxxxxxxxx
+GITHUB_OWNER=myorg  # Optional: default owner for repositories
+
+# JIRA credentials (optional - only if using JIRA integration)
+JIRA_ACCESS_USER=your.email@company.com
+JIRA_ACCESS_TOKEN=xxxxxxxxxxxxxxxxxxxx
+
+# Other optional tokens
+CLICKUP_TOKEN=pk_xxxxxxxxxxxx
+LINEAR_TOKEN=lin_api_xxxxxxxxxxxx
+```
+
+#### Step 2: Reference in YAML configuration
+
+Use `${VARIABLE_NAME}` syntax in your YAML to reference environment variables:
+
+```yaml
+# config.yaml
+version: "1.0"
+
+github:
+  token: "${GITHUB_TOKEN}"        # Required
+  owner: "${GITHUB_OWNER}"        # Optional
+  organization: "${GITHUB_ORG}"   # Optional (for org-based discovery)
+
+# Optional: JIRA integration
+jira:
+  access_user: "${JIRA_ACCESS_USER}"
+  access_token: "${JIRA_ACCESS_TOKEN}"
+  base_url: "https://yourcompany.atlassian.net"
+
+# Optional: Configure which JIRA fields contain story points
+jira_integration:
+  story_point_fields:
+    - "Story Points"
+    - "customfield_10016"  # Your custom field ID
+```
+
+#### Important Notes:
+
+- **Never commit `.env` files** to version control (add to `.gitignore`)
+- If credentials are not found in the `.env` file, the tool will exit with an informative error
+- The `.env` file must be in the same directory as your YAML configuration
+- All configured services must have corresponding environment variables set
+
+### Organization vs Repository-based Setup
+
+GitFlow Analytics supports two main configuration approaches:
+
+#### Organization-based Configuration (Recommended)
+
+Automatically discovers all non-archived repositories from a GitHub organization:
+
+```yaml
+version: "1.0"
+
+github:
+  token: "${GITHUB_TOKEN}"
+  organization: "myorg"  # Your GitHub organization name
+
+# Optional: Customize analysis settings
+analysis:
+  story_point_patterns:
+    - "(?:story\\s*points?|sp|pts?)\\s*[:=]\\s*(\\d+)"
+  
+  exclude:
+    authors:
+      - "dependabot[bot]"
+      - "github-actions[bot]"
+```
+
+**Benefits:**
+- Automatically discovers new repositories as they're added to the organization
+- No need to manually configure each repository
+- Simplified configuration management
+- Perfect for teams with many repositories
+
+**Requirements:**
+- Your GitHub token must have organization read access
+- Repositories will be automatically cloned to local directories if they don't exist
+
+#### Repository-based Configuration
+
+Manually specify each repository to analyze:
+
+```yaml
+version: "1.0"
+
+github:
+  token: "${GITHUB_TOKEN}"
+  owner: "${GITHUB_OWNER}"  # Default owner for repositories
+
+repositories:
+  - name: "frontend"
+    path: "~/repos/frontend"
+    github_repo: "myorg/frontend"
+    project_key: "FRONTEND"
+    
+  - name: "backend"
+    path: "~/repos/backend"
+    github_repo: "myorg/backend"
+    project_key: "BACKEND"
+
+analysis:
+  story_point_patterns:
+    - "(?:story\\s*points?|sp|pts?)\\s*[:=]\\s*(\\d+)"
+```
+
+**Benefits:**
+- Fine-grained control over which repositories to analyze
+- Custom project keys and local paths
+- Works with mixed-ownership repositories
+- Compatible with existing configurations
+
+### Directory Defaults
+
+GitFlow Analytics now defaults cache and report directories to be relative to the configuration file location:
+
+- **Reports**: Default to same directory as config file (unless overridden with `--output`)
+- **Cache**: Default to `.gitflow-cache/` in config file directory
+- **Backward compatibility**: Absolute paths in configuration continue to work as before
+
+Example directory structure:
+```
+/project/
+├── config.yaml          # Configuration file
+├── weekly_metrics.csv    # Reports generated here by default
+├── summary.csv
+└── .gitflow-cache/       # Cache directory
+    ├── gitflow_cache.db
+    └── identities.db
+```
+
+## Command Line Interface
+
+### Main Commands
+
+```bash
+# Analyze repositories
+gitflow-analytics analyze -c config.yaml --weeks 12 --output ./reports
+
+# Show cache statistics
+gitflow-analytics cache-stats -c config.yaml
+
+# List known developers
+gitflow-analytics list-developers -c config.yaml
+
+# Merge developer identities
+gitflow-analytics merge-identity -c config.yaml dev1_id dev2_id
+
+# Discover JIRA story point fields
+gitflow-analytics discover-jira-fields -c config.yaml
+```
+
+### Options
+
+- `--weeks, -w`: Number of weeks to analyze (default: 12)
+- `--output, -o`: Output directory for reports (default: ./reports)
+- `--anonymize`: Anonymize developer information
+- `--no-cache`: Disable caching for fresh analysis
+- `--clear-cache`: Clear cache before analysis
+- `--validate-only`: Validate configuration without running
+
+## Complete Configuration Example
+
+Here's a complete example showing `.env` file and corresponding YAML configuration:
+
+### `.env` file
+```bash
+# GitHub Configuration
+GITHUB_TOKEN=ghp_xxxxxxxxxxxxxxxxxxxx
+GITHUB_ORG=EWTN-Global
+
+# JIRA Configuration
+JIRA_ACCESS_USER=developer@ewtn.com
+JIRA_ACCESS_TOKEN=ATATT3xxxxxxxxxxx
+
+# Optional: Other integrations
+# CLICKUP_TOKEN=pk_xxxxxxxxxxxx
+# LINEAR_TOKEN=lin_api_xxxxxxxxxxxx
+```
+
+### `config.yaml` file
+```yaml
+version: "1.0"
+
+# GitHub configuration with organization discovery
+github:
+  token: "${GITHUB_TOKEN}"
+  organization: "${GITHUB_ORG}"
+
+# JIRA integration for story points
+jira:
+  access_user: "${JIRA_ACCESS_USER}"
+  access_token: "${JIRA_ACCESS_TOKEN}"
+  base_url: "https://ewtn.atlassian.net"
+
+jira_integration:
+  enabled: true
+  fetch_story_points: true
+  story_point_fields:
+    - "Story point estimate"     # Your field name
+    - "customfield_10016"        # Fallback field ID
+
+# Analysis configuration
+analysis:
+  # Only track JIRA tickets (ignore GitHub issues, etc.)
+  ticket_platforms:
+    - jira
+  
+  # Exclude bot commits and boilerplate files
+  exclude:
+    authors:
+      - "dependabot[bot]"
+      - "renovate[bot]"
+    paths:
+      - "**/node_modules/**"
+      - "**/*.min.js"
+      - "**/package-lock.json"
+  
+  # Developer identity consolidation
+  identity:
+    similarity_threshold: 0.85
+    manual_mappings:
+      - primary_email: "john.doe@company.com"
+        aliases:
+          - "jdoe@oldcompany.com"
+          - "john@personal.com"
+
+# Output configuration
+output:
+  directory: "./reports"
+  formats:
+    - csv
+    - markdown
+```
+
+## Output Reports
+
+The tool generates three CSV reports:
+
+1. **Weekly Metrics** (`weekly_metrics_YYYYMMDD.csv`)
+   - Week-by-week developer productivity
+   - Story points, commits, lines changed
+   - Ticket coverage percentages
+   - Per-project breakdown
+
+2. **Summary Statistics** (`summary_YYYYMMDD.csv`)
+   - Overall project statistics
+   - Platform-specific ticket counts
+   - Top contributors
+
+3. **Developer Report** (`developers_YYYYMMDD.csv`)
+   - Complete developer profiles
+   - Total contributions
+   - Identity aliases
+
+## Story Point Patterns
+
+Configure custom regex patterns to match your team's story point format:
+
+```yaml
+story_point_patterns:
+  - "SP: (\\d+)"           # SP: 5
+  - "\\[([0-9]+) pts\\]"   # [3 pts]
+  - "estimate: (\\d+)"     # estimate: 8
+```
+
+## Ticket Platform Support
+
+Automatically detects and tracks tickets from:
+- **JIRA**: `PROJ-123`
+- **GitHub**: `#123`, `GH-123`
+- **ClickUp**: `CU-abc123`
+- **Linear**: `ENG-123`
+
+### JIRA Integration
+
+GitFlow Analytics can fetch story points directly from JIRA tickets. Configure your JIRA instance:
+
+```yaml
+jira:
+  access_user: "${JIRA_ACCESS_USER}"
+  access_token: "${JIRA_ACCESS_TOKEN}"
+  base_url: "https://your-company.atlassian.net"
+
+jira_integration:
+  enabled: true
+  story_point_fields:
+    - "Story point estimate"  # Your custom field name
+    - "customfield_10016"     # Or use field ID
+```
+
+To discover your JIRA story point fields:
+```bash
+gitflow-analytics discover-jira-fields -c config.yaml
+```
+
+## Caching
+
+The tool uses SQLite for intelligent caching:
+- Commit analysis results
+- Developer identity mappings
+- Pull request data
+
+Cache is automatically managed with configurable TTL.
+
+## Developer Identity Resolution
+
+Intelligently merges developer identities across:
+- Different email addresses
+- Name variations
+- GitHub usernames
+
+Manual overrides supported in configuration.
+
+## Contributing
+
+Contributions are welcome! Please feel free to submit a Pull Request.
+
+## License
+
+This project is licensed under the MIT License - see the LICENSE file for details.

gitflow_analytics-1.0.1.dist-info/RECORD

@@ -0,0 +1,31 @@
+gitflow_analytics/__init__.py,sha256=9g64-8GIadOL3mCDsxHPMIlUhztZAx_nUISQtRotsuY,682
+gitflow_analytics/_version.py,sha256=d6tbYJNPyd-1yr5YWMYdu12zn6-tSRgYnpW5-dGvQWA,136
+gitflow_analytics/cli.py,sha256=1zC5kOSFKtgGHaew6JOjezRUXh3FrVmZEYE2mu5h0QY,21103
+gitflow_analytics/config.py,sha256=xQpsQTKtTU5L3k44YG3grtXl-b4miL9l5GcPV0w5Vkc,15896
+gitflow_analytics/core/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
+gitflow_analytics/core/analyzer.py,sha256=7DRofL9aRdafuRaTxKne0h42QAhdDn245-cIhkDyNaQ,10379
+gitflow_analytics/core/branch_mapper.py,sha256=p1MzezL2aMjhVX0672aC9Zc_1QPVnKmw1EEn4CSZTCc,7603
+gitflow_analytics/core/cache.py,sha256=nAWdkT210mrsMrpC50pCYXJ5e7mi5YzgrgB5Bd0UXOo,11641
+gitflow_analytics/core/identity.py,sha256=FXD5aeMbf1yyFwDKQqu943kHIMRLbb7lclw1m421qF4,17046
+gitflow_analytics/extractors/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
+gitflow_analytics/extractors/base.py,sha256=EIs8udjsJOMJMuqo6GJD9m-LQ-bmXuD8Ofdxr9KHYzQ,1208
+gitflow_analytics/extractors/story_points.py,sha256=2NUViohigV5QHMw5U_NMwEuNd4pFLVuFYphM7ZliZ-Y,5038
+gitflow_analytics/extractors/tickets.py,sha256=pjexGozeZlxy0oG6D-qxtkWrQiWbdU2PU3CmdJxIZfY,6655
+gitflow_analytics/integrations/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
+gitflow_analytics/integrations/github_integration.py,sha256=snRjPKZXBP0XK_vProHJeqRWDAxAVbuGEbRf1yWsZew,6719
+gitflow_analytics/integrations/jira_integration.py,sha256=UE8UmMt90Py2PZTldAjLhBYHhFF81F5gwAuvjtHAI18,10549
+gitflow_analytics/integrations/orchestrator.py,sha256=72l6mt2MGk5eJBO1GuwUEMg_K16SeK8fzp1TNlm8wbQ,5688
+gitflow_analytics/metrics/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
+gitflow_analytics/metrics/dora.py,sha256=hn99XATw-lWr8RdQQb5u7XwT-tAZs0CC5Qbj0xOHkWw,12709
+gitflow_analytics/models/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
+gitflow_analytics/models/database.py,sha256=y93oyZHe1EyYX9YYgI2jDnuXtBG4_BsvJx7ei9mRgl0,5521
+gitflow_analytics/reports/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
+gitflow_analytics/reports/analytics_writer.py,sha256=FoXLcdS11q6DekB2QfR-1J30gUQkARfiR-hyWZZO5hw,19496
+gitflow_analytics/reports/csv_writer.py,sha256=SgQLa9mNc-pLhLwy1hhttMjKPTXcRYvOaUwvUD1WI84,13021
+gitflow_analytics/reports/narrative_writer.py,sha256=GKBdbFL6_Qwfi8xXsD5C_inFf12h4_gy-9QasanTv1Q,12879
+gitflow_analytics-1.0.1.dist-info/licenses/LICENSE,sha256=xwvSwY1GYXpRpmbnFvvnbmMwpobnrdN9T821sGvjOY0,1066
+gitflow_analytics-1.0.1.dist-info/METADATA,sha256=yy2hzjV1Y1DdhXUn7MuOdnyjVxYIZ5u306ux_VZYKFk,12677
+gitflow_analytics-1.0.1.dist-info/WHEEL,sha256=_zCd3N1l69ArxyTb8rzEoP9TpbYXkqRFSNOD5OuxnTs,91
+gitflow_analytics-1.0.1.dist-info/entry_points.txt,sha256=a3y8HnfLOvK1QVOgAkDY6VQXXm3o9ZSQRZrpiaS3hEM,65
+gitflow_analytics-1.0.1.dist-info/top_level.txt,sha256=CQyxZXjKvpSB1kgqqtuE0PCRqfRsXZJL8JrYpJKtkrk,18
+gitflow_analytics-1.0.1.dist-info/RECORD,,

gitflow_analytics-1.0.0.dist-info/METADATA

@@ -1,201 +0,0 @@
-Metadata-Version: 2.4
-Name: gitflow-analytics
-Version: 1.0.0
-Summary: Analyze Git repositories for developer productivity insights
-Author-email: Bob Matyas <bobmatnyc@gmail.com>
-License: MIT
-Project-URL: Homepage, https://github.com/bobmatnyc/gitflow-analytics
-Project-URL: Documentation, https://github.com/bobmatnyc/gitflow-analytics/blob/main/README.md
-Project-URL: Repository, https://github.com/bobmatnyc/gitflow-analytics
-Project-URL: Issues, https://github.com/bobmatnyc/gitflow-analytics/issues
-Keywords: git,analytics,productivity,metrics,development
-Classifier: Development Status :: 5 - Production/Stable
-Classifier: Intended Audience :: Developers
-Classifier: License :: OSI Approved :: MIT License
-Classifier: Programming Language :: Python :: 3
-Classifier: Programming Language :: Python :: 3.8
-Classifier: Programming Language :: Python :: 3.9
-Classifier: Programming Language :: Python :: 3.10
-Classifier: Programming Language :: Python :: 3.11
-Classifier: Programming Language :: Python :: 3.12
-Classifier: Topic :: Software Development :: Version Control :: Git
-Classifier: Topic :: Software Development :: Quality Assurance
-Requires-Python: >=3.8
-Description-Content-Type: text/markdown
-License-File: LICENSE
-Requires-Dist: click>=8.1
-Requires-Dist: gitpython>=3.1
-Requires-Dist: tqdm>=4.65
-Requires-Dist: sqlalchemy>=2.0
-Requires-Dist: pandas>=2.0
-Requires-Dist: pyyaml>=6.0
-Requires-Dist: python-dateutil>=2.8
-Provides-Extra: dev
-Requires-Dist: pytest>=7.0; extra == "dev"
-Requires-Dist: pytest-cov>=4.0; extra == "dev"
-Requires-Dist: pytest-mock>=3.0; extra == "dev"
-Requires-Dist: ruff>=0.1.0; extra == "dev"
-Requires-Dist: mypy>=1.0; extra == "dev"
-Requires-Dist: black>=23.0; extra == "dev"
-Provides-Extra: github
-Requires-Dist: pygithub>=1.58; extra == "github"
-Provides-Extra: all
-Requires-Dist: gitflow-analytics[github]; extra == "all"
-Dynamic: license-file
-
-# GitFlow Analytics
-
-A Python package for analyzing Git repositories to generate comprehensive developer productivity reports. It extracts data directly from Git history and GitHub APIs, providing weekly summaries, productivity insights, and gap analysis.
-
-## Features
-
-- 🚀 **Multi-repository analysis** with project grouping
-- 👥 **Developer identity resolution** and normalization
-- 📊 **Work volume analysis** (absolute vs relative effort)
-- 🎯 **Story point extraction** from commit messages and PR descriptions
-- 🎫 **Multi-platform ticket tracking** (JIRA, GitHub Issues, ClickUp, Linear)
-- 📈 **Weekly CSV reports** with productivity metrics
-- 🔒 **Data anonymization** for external sharing
-- ⚡ **Smart caching** for fast repeated analyses
-- 🔄 **Batch processing** for large repositories
-
-## Quick Start
-
-### Installation
-
-```bash
-pip install gitflow-analytics
-```
-
-### Basic Usage
-
-1. Create a configuration file (`config.yaml`):
-
-```yaml
-version: "1.0"
-
-github:
-  token: "${GITHUB_TOKEN}"
-  owner: "${GITHUB_OWNER}"
-
-repositories:
-  - name: "frontend"
-    path: "~/repos/frontend"
-    github_repo: "myorg/frontend"
-    project_key: "FRONTEND"
-    
-  - name: "backend"
-    path: "~/repos/backend"
-    github_repo: "myorg/backend"
-    project_key: "BACKEND"
-
-analysis:
-  story_point_patterns:
-    - "(?:story\\s*points?|sp|pts?)\\s*[:=]\\s*(\\d+)"
-    - "\\[(\\d+)\\s*(?:sp|pts?)\\]"
-```
-
-2. Set environment variables:
-
-```bash
-export GITHUB_TOKEN=your_github_token
-export GITHUB_OWNER=your_github_org
-```
-
-3. Run the analysis:
-
-```bash
-gitflow-analytics analyze -c config.yaml
-```
-
-## Command Line Interface
-
-### Main Commands
-
-```bash
-# Analyze repositories
-gitflow-analytics analyze -c config.yaml --weeks 12 --output ./reports
-
-# Show cache statistics
-gitflow-analytics cache-stats -c config.yaml
-
-# List known developers
-gitflow-analytics list-developers -c config.yaml
-
-# Merge developer identities
-gitflow-analytics merge-identity -c config.yaml dev1_id dev2_id
-```
-
-### Options
-
-- `--weeks, -w`: Number of weeks to analyze (default: 12)
-- `--output, -o`: Output directory for reports (default: ./reports)
-- `--anonymize`: Anonymize developer information
-- `--no-cache`: Disable caching for fresh analysis
-- `--clear-cache`: Clear cache before analysis
-- `--validate-only`: Validate configuration without running
-
-## Output Reports
-
-The tool generates three CSV reports:
-
-1. **Weekly Metrics** (`weekly_metrics_YYYYMMDD.csv`)
-   - Week-by-week developer productivity
-   - Story points, commits, lines changed
-   - Ticket coverage percentages
-   - Per-project breakdown
-
-2. **Summary Statistics** (`summary_YYYYMMDD.csv`)
-   - Overall project statistics
-   - Platform-specific ticket counts
-   - Top contributors
-
-3. **Developer Report** (`developers_YYYYMMDD.csv`)
-   - Complete developer profiles
-   - Total contributions
-   - Identity aliases
-
-## Story Point Patterns
-
-Configure custom regex patterns to match your team's story point format:
-
-```yaml
-story_point_patterns:
-  - "SP: (\\d+)"           # SP: 5
-  - "\\[([0-9]+) pts\\]"   # [3 pts]
-  - "estimate: (\\d+)"     # estimate: 8
-```
-
-## Ticket Platform Support
-
-Automatically detects and tracks tickets from:
-- **JIRA**: `PROJ-123`
-- **GitHub**: `#123`, `GH-123`
-- **ClickUp**: `CU-abc123`
-- **Linear**: `ENG-123`
-
-## Caching
-
-The tool uses SQLite for intelligent caching:
-- Commit analysis results
-- Developer identity mappings
-- Pull request data
-
-Cache is automatically managed with configurable TTL.
-
-## Developer Identity Resolution
-
-Intelligently merges developer identities across:
-- Different email addresses
-- Name variations
-- GitHub usernames
-
-Manual overrides supported in configuration.
-
-## Contributing
-
-Contributions are welcome! Please feel free to submit a Pull Request.
-
-## License
-
-This project is licensed under the MIT License - see the LICENSE file for details.