GitHub Project Management Integration

GitHub is where code lives, but project management needs extend beyond repository features. GitScrum's GitHub integration bridges this gap by synchronizing issues, pull requests, and commits with your project boards, providing comprehensive visibility across development and management activities.

Integration Benefits

Setting Up GitHub Integration

INTEGRATION SETUP STEPS

1. CONNECT GITHUB ACCOUNT
┌─────────────────────────────────────────────────┐
│  GitScrum → Settings → Integrations → GitHub    │
│                                                 │
│  • Authorize GitScrum app                       │
│  • Select repositories                          │
│  • Configure permissions                        │
└─────────────────────────────────────────────────┘

2. MAP REPOSITORIES TO PROJECTS
┌─────────────────────────────────────────────────┐
│  Project: Mobile App                            │
│  ├── frontend-mobile (GitHub repo)              │
│  └── api-backend (GitHub repo)                  │
│                                                 │
│  All activity from these repos → this project   │
└─────────────────────────────────────────────────┘

3. CONFIGURE AUTOMATION
┌─────────────────────────────────────────────────┐
│  PR Opened → Task status: In Review             │
│  PR Merged → Task status: Done                  │
│  CI Failed → Add label: needs-fix               │
└─────────────────────────────────────────────────┘

Workflow Integration

DEVELOPER WORKFLOW WITH INTEGRATION

┌─────────────────────────────────────────────────┐
│                   GITSCRUM                      │
│  ┌──────────────────────────────────────────┐   │
│  │ Task: GS-123                             │   │
│  │ "Add user authentication"                │   │
│  │                                          │   │
│  │ Status: In Review                        │   │
│  │                                          │   │
│  │ Timeline:                                │   │
│  │ ├── 9:00 AM  Branch created              │   │
│  │ ├── 10:30 AM Commit: Add login API       │   │
│  │ ├── 11:15 AM Commit: Add tests           │   │
│  │ ├── 11:30 AM PR #42 opened              │   │
│  │ ├── 2:00 PM  Review requested            │   │
│  │ └── 3:30 PM  Changes requested           │   │
│  │                                          │   │
│  │ Linked PR: #42 (awaiting review)         │   │
│  └──────────────────────────────────────────┘   │
│                      ↕                          │
│                  SYNCED                         │
│                      ↕                          │
│                   GITHUB                        │
│  ┌──────────────────────────────────────────┐   │
│  │ PR #42: GS-123 Add user authentication   │   │
│  │                                          │   │
│  │ Description:                             │   │
│  │ Implements login flow per task GS-123    │   │
│  │ [Link to GitScrum task]                  │   │
│  │                                          │   │
│  │ Status: Review requested                 │   │
│  │ Checks: ✓ CI passing                     │   │
│  └──────────────────────────────────────────┘   │
└─────────────────────────────────────────────────┘

Commit Linking

COMMIT TO TASK LINKING

COMMIT MESSAGE FORMAT:
┌─────────────────────────────────────────────────┐
│  GS-123: Add user login endpoint                │
│                                                 │
│  - Implement POST /api/auth/login               │
│  - Add JWT token generation                     │
│  - Include rate limiting                        │
│                                                 │
│  Closes GS-123                                  │
└─────────────────────────────────────────────────┘

RESULT IN GITSCRUM:
┌─────────────────────────────────────────────────┐
│  Task GS-123 Timeline:                          │
│                                                 │
│  [Commit] abc1234 by @developer                 │
│  "Add user login endpoint"                      │
│  +145 lines, -12 lines                          │
│  3 files changed                                │
└─────────────────────────────────────────────────┘

PR Review Workflow

PR STATUS FLOW

GitHub PR State        →    GitScrum Task State
───────────────────────────────────────────────
Draft                  →    In Progress
Ready for Review       →    In Review
Changes Requested      →    In Review (flagged)
Approved               →    Ready to Merge
Merged                 →    Done
Closed (not merged)    →    To Do (returned)

REVIEW VISIBILITY:
┌─────────────────────────────────────────────────┐
│  Task: GS-123                                   │
│                                                 │
│  PR Status: Changes Requested                   │
│  Reviewer: @seniordev                           │
│  Comment: "Need error handling for edge case"   │
│                                                 │
│  CI Status: ✓ Passing                           │
│  Code Coverage: 87%                             │
└─────────────────────────────────────────────────┘

Best Practices

1. Use task IDs consistently in branches and PRs
2. Configure status automation to reduce manual updates
3. Link repositories to projects for proper context
4. Enable PR templates that include task links
5. Review task context before code review
6. Sync only necessary events to avoid noise
7. Use GitHub Actions with GitScrum webhooks
8. Archive completed work with full Git history

Anti-Patterns

✗ Using both GitHub Issues and GitScrum separately
✗ Manual status updates when automation exists
✗ PRs without task references
✗ No repository-to-project mapping
✗ Ignoring CI status in task view
✗ Too many notification syncs (noise)

Related Solutions

• Git Workflow Integration
• GitLab Workflow Automation
• Setting Up GitScrum Integrations