This Go application connects to a MySQL database and communicates with the GitHub API to track pull requests, their code diffs, patches, reviews, and comments across multiple repositories.

• Multi-repository tracking support
• Detailed PR tracking including:
  • Code diffs and patches per file
  • PR comments (both review comments and issue comments)
  • PR reviews and their state (approved, changes requested, etc.)
  • File changes statistics (files changed, additions, deletions)
• Web UI for visualizing PR data:
  • Dashboard with repository statistics
  • Pull request listings with filtering
  • Code change analytics
  • Contributor insights
  • Review analytics

• Docker and Docker Compose
• GitHub Personal Access Token with repo permissions

The application is configured using environment variables:

1. Clone this repository
2. Create a .env file with your GitHub credentials:

GITHUB_TOKEN=your_github_token
GITHUB_REPOS=owner1/repo1,owner2/repo2,owner3/repo3
FETCH_SINCE_DAYS=30
UPDATE_INTERVAL=3600

3. Build and start the application using Docker Compose:

docker-compose up -d

4. Access the web UI at http://localhost:5000

If you see errors like Unknown column 'files_changed' in 'field list' or Unknown column 'repo_owner' in 'field list', your database schema needs to be updated to match the application's expectations. You can fix this by:

1. Stopping all containers:

   docker-compose down

2. Removing the MySQL volume to start fresh:

   docker volume rm github-pr-tracker_mysql-data

3. Restarting everything:

   docker-compose up -d

To view logs for a specific service:

# For the Go application
docker logs github-pr-app

# For the web UI
docker logs github-pr-web-ui

# For the scheduler
docker logs github-pr-scheduler

# For the MySQL database
docker logs github-pr-mysql

To follow logs in real-time:

docker logs -f github-pr-app

The application creates the following tables:

Once the application has run, you can connect to the MySQL database and run queries:

-- Get top repositories by PR count
SELECT 
    repo_owner, 
    repo_name, 
    COUNT(*) as pr_count,
    SUM(additions) as total_additions,
    SUM(deletions) as total_deletions
FROM 
    pull_requests
GROUP BY 
    repo_owner, repo_name
ORDER BY 
    pr_count DESC;

-- Get top contributors across all repositories
SELECT 
    user_login, 
    COUNT(*) as pr_count,
    SUM(additions) as total_additions,
    SUM(deletions) as total_deletions
FROM 
    pull_requests
GROUP BY 
    user_login
ORDER BY 
    pr_count DESC
LIMIT 10;

-- Get PRs with the most review activity
SELECT 
    pr.repo_owner,
    pr.repo_name,
    pr.number, 
    pr.title, 
    COUNT(r.id) as review_count,
    SUM(CASE WHEN r.state = 'APPROVED' THEN 1 ELSE 0 END) as approvals,
    SUM(CASE WHEN r.state = 'CHANGES_REQUESTED' THEN 1 ELSE 0 END) as change_requests
FROM 
    pull_requests pr
JOIN 
    pr_reviews r ON pr.id = r.pr_id
GROUP BY 
    pr.id
ORDER BY 
    review_count DESC
LIMIT 10;

-- Get most modified files
SELECT 
    p.filename,
    COUNT(DISTINCT pr.id) as pr_count,
    SUM(p.changes) as total_changes,
    SUM(p.additions) as total_additions,
    SUM(p.deletions) as total_deletions
FROM 
    pr_patches p
JOIN
    pull_requests pr ON p.pr_id = pr.id
GROUP BY 
    p.filename
ORDER BY 
    total_changes DESC
LIMIT 20;

This application can be extended in several ways:

1. Add more metrics and analytics:

   • PR merge time analysis
   • Review turnaround time
   • Code quality metrics
   • Team collaboration patterns

2. Enhanced visualizations:

   • Team-based statistics
   • Code hotspots heat maps
   • Developer network graphs

3. Integration with other systems:

   • CI/CD status tracking
   • Issue tracker correlation
   • Slack/Discord notifications

4. Additional GitHub features:

   • Workflow runs tracking
   • Issue tracking
   • Release management