cardosofelipe/syndarix
1
0
Fork 0
forked from cardosofelipe/fast-next-template
Code Issues 18 Pull Requests Wiki Activity

feat(mcp): Git Operations MCP - GitHub Provider (Optional) #110

New Issue
Open
opened 2026-01-06 19:19:38 +00:00 by cardosofelipe · 1 comment
cardosofelipe commented 2026-01-06 19:19:38 +00:00
Owner
Copy Link

Parent Issue

Part of #58 (Git Operations MCP Server)

Summary

Implement the GitHub provider using PyGithub for remote Git operations. This is a follow-up after Gitea provider is working.

Tasks

GitHubProvider Class (providers/github.py)

  • Create GitHubProvider class implementing GitProvider protocol
  • Implement API client with token authentication
  • Implement create_pull_request() method
  • Implement list_pull_requests() method
  • Implement get_pull_request() method
  • Implement merge_pull_request() method
  • Implement close_pull_request() method
  • Implement add_pr_comment() method
  • Implement add_pr_reviewer() method
  • Implement get_pr_diff() method
  • Implement list_branches() method
  • Implement create_branch() method
  • Implement delete_branch() method

GitHub-Specific Features

  • Handle GitHub's rate limiting (different limits than Gitea)
  • Add pagination support
  • Support GitHub Enterprise (custom base URL)

Provider Factory

  • Create ProviderFactory class
  • Auto-detect provider from repo URL
  • Support provider override in configuration
  • Cache provider instances per repository

Testing

  • Unit tests with mocked GitHub API
  • Test all PR operations
  • Test GitHub Enterprise support
  • Achieve >90% coverage

Acceptance Criteria

  • All GitHub API operations work correctly
  • Rate limiting handled properly
  • Provider factory auto-detects GitHub repos
  • GitHub Enterprise supported
  • All tests pass

Dependencies

  • Depends on: #108 (Gitea Provider) - patterns established

Labels

  • mcp
  • phase-2
  • backend
  • optional
## Parent Issue Part of #58 (Git Operations MCP Server) ## Summary Implement the GitHub provider using PyGithub for remote Git operations. This is a follow-up after Gitea provider is working. ## Tasks ### GitHubProvider Class (`providers/github.py`) - [ ] Create `GitHubProvider` class implementing `GitProvider` protocol - [ ] Implement API client with token authentication - [ ] Implement `create_pull_request()` method - [ ] Implement `list_pull_requests()` method - [ ] Implement `get_pull_request()` method - [ ] Implement `merge_pull_request()` method - [ ] Implement `close_pull_request()` method - [ ] Implement `add_pr_comment()` method - [ ] Implement `add_pr_reviewer()` method - [ ] Implement `get_pr_diff()` method - [ ] Implement `list_branches()` method - [ ] Implement `create_branch()` method - [ ] Implement `delete_branch()` method ### GitHub-Specific Features - [ ] Handle GitHub's rate limiting (different limits than Gitea) - [ ] Add pagination support - [ ] Support GitHub Enterprise (custom base URL) ### Provider Factory - [ ] Create `ProviderFactory` class - [ ] Auto-detect provider from repo URL - [ ] Support provider override in configuration - [ ] Cache provider instances per repository ### Testing - [ ] Unit tests with mocked GitHub API - [ ] Test all PR operations - [ ] Test GitHub Enterprise support - [ ] Achieve >90% coverage ## Acceptance Criteria - [ ] All GitHub API operations work correctly - [ ] Rate limiting handled properly - [ ] Provider factory auto-detects GitHub repos - [ ] GitHub Enterprise supported - [ ] All tests pass ## Dependencies - Depends on: #108 (Gitea Provider) - patterns established ## Labels - mcp - phase-2 - backend - optional
cardosofelipe commented 2026-01-06 19:55:50 +00:00
Author
Owner
Copy Link

Implementation Complete

The GitHub provider has been implemented with full feature parity to the Gitea provider:

Features Implemented

PR Operations:

  • Create PR with draft support
  • Get PR details
  • List PRs with state filtering
  • Merge PR (merge, squash, rebase strategies)
  • Update PR (title, body, state, labels, assignees)
  • Close PR without merging

Branch Operations:

  • Get branch info via API
  • Delete remote branch

Collaboration:

  • Add/remove labels
  • Add comments
  • List comments
  • Request reviewers

Error Handling:

  • Authentication errors (401)
  • Permission errors (403)
  • Rate limit detection
  • API errors with messages

Server Integration

  • Auto-detection of GitHub URLs (github.com or Enterprise)
  • Automatic token selection for clone/push based on repo URL
  • Health check includes GitHub connectivity status
  • GitHub provider initialized when GIT_OPS_GITHUB_TOKEN is set

Tests

39 comprehensive tests covering:

  • Connection and authentication
  • All PR operations
  • Branch operations
  • Label and comment operations
  • Error handling scenarios
  • PR data parsing

Commit: 1779239

Ready for code review.

## Implementation Complete The GitHub provider has been implemented with full feature parity to the Gitea provider: ### Features Implemented **PR Operations:** - Create PR with draft support - Get PR details - List PRs with state filtering - Merge PR (merge, squash, rebase strategies) - Update PR (title, body, state, labels, assignees) - Close PR without merging **Branch Operations:** - Get branch info via API - Delete remote branch **Collaboration:** - Add/remove labels - Add comments - List comments - Request reviewers **Error Handling:** - Authentication errors (401) - Permission errors (403) - Rate limit detection - API errors with messages ### Server Integration - Auto-detection of GitHub URLs (github.com or Enterprise) - Automatic token selection for clone/push based on repo URL - Health check includes GitHub connectivity status - GitHub provider initialized when `GIT_OPS_GITHUB_TOKEN` is set ### Tests 39 comprehensive tests covering: - Connection and authentication - All PR operations - Branch operations - Label and comment operations - Error handling scenarios - PR data parsing **Commit:** 1779239 Ready for code review.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
agents
Agent orchestration
 architecture
Architectural decisions
 backend
Backend work
 blocked
Blocked by dependency
 database
Database/migrations
 design
UI/UX design work
 devops
DevOps/Infrastructure work
 epic
Epic/parent issue
 frontend
Frontend work
 infrastructure
Infrastructure / DevOps
 mcp
MCP related
 phase-0
Phase 0: Foundation
 phase-1
Phase 1: Core Platform
 phase-2
Phase 2: MCP Integration
 priority:high
High priority
 spike
Architecture spike / research task
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
cardosofelipe
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: cardosofelipe/syndarix#110
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?