DirectApp GitHub Setup

Complete GitHub Project configuration with issue templates, automation, and workflows.

---

📁 Structure

.github/
├── ISSUE_TEMPLATE/
│   ├── bug.yml              # Bug report template
│   ├── feature.yml          # Feature request template
│   ├── infrastructure.yml   # Infrastructure task template
│   └── config.yml           # Template configuration
├── scripts/
│   ├── setup-project.sh           # Create new GitHub Project
│   └── create-initial-issues.sh   # Populate with initial issues
├── PROJECT_TEMPLATE.md      # Complete project documentation
└── README.md                # This file

---

🚀 Quick Start

1. Create New GitHub Project

# Make script executable
chmod +x .github/scripts/setup-project.sh

# Run setup
./.github/scripts/setup-project.sh

This creates a new GitHub Project with:

• Custom fields (Priority, Size, Component, Environment, etc.)
• Labels (priority, type, component, status)
• Proper configuration

2. Add Project README (Manual in UI)

IMPORTANT: Add the project README to provide context and documentation.

1. Open project: gh project view 2 --owner gumpen-app --web
2. Click the ... menu (top right) → Settings
3. Under README, click Add README
4. Copy content from .github/PROJECT_README.md and paste
5. Click Save

This provides project overview, sprint info, workflow integration, and quick links.

3. Configure Project Views (Manual in UI)

After adding the README, create these views in the project:

Board View (Default)

• Group by: Status
• Filter: Current sprint
• Columns: Backlog → Ready → In Progress → Review → Done

Table View (All Issues)

• Show all columns
• Sort by: Priority, Status
• Filter: None

Roadmap View (Timeline)

• Group by: Epic
• Date field: Sprint
• Show next 3 sprints

My Work (Personal)

• Filter: Assignee = @me, Status != Done
• Group by: Status

Blocked Items

• Filter: Status = Blocked
• Sort by: Priority

4. Set Up Automation Rules (Manual in UI)

Configure these automations in Project Settings → Workflows:

# When PR is created → Move to Review
trigger: pull_request.opened
action: set Status = 👀 Review

# When PR is merged → Move to Done
trigger: pull_request.merged
action: set Status = ✅ Done

# When issue assigned → Move to In Progress
trigger: issue.assigned
action: set Status = 🏃 In Progress

# When labeled "blocked" → Move to Blocked
trigger: issue.labeled (blocked)
action: set Status = 🚫 Blocked

5. Create Initial Infrastructure Issues

# Make script executable
chmod +x .github/scripts/create-initial-issues.sh

# Create issues
./.github/scripts/create-initial-issues.sh

This creates 7 foundational issues:

• Phase 1: Core Infrastructure (3 issues)
• Phase 2: Testing & CI/CD (2 issues)
• Phase 3: Schema & Data (2 issues)

---

📊 Project Structure

Custom Fields

Workflow States

📋 Backlog → 🔜 Ready → 🏃 In Progress → 👀 Review → ✅ Done
                           ↓
                        🚫 Blocked

Labels

Priority: priority: critical, priority: high, priority: medium, priority: low

Type: type: bug, type: feature, type: enhancement, type: docs, type: chore

Component: component: workflow, component: deployment, component: schema, component: api, component: ui, component: extensions

Status: blocked, needs-review, needs-testing, ready-to-merge

---

📝 Issue Templates

Feature Request (feature.yml)

For new features and enhancements

• User story format
• Acceptance criteria
• Priority and size estimation
• Component assignment

Bug Report (bug.yml)

For bugs and issues

• Steps to reproduce
• Expected vs actual behavior
• Environment tracking
• Screenshots and logs

Infrastructure Task (infrastructure.yml)

For deployment and configuration

• Environment specification
• Configuration details
• Verification steps
• Rollback plan

---

🔄 Workflow Integration

Using with /core:work

# Start work on next task
/core:work

# This will:
# 1. Query GitHub Project for next Ready task
# 2. Create feature branch
# 3. Start session tracking
# 4. Set task to "In Progress"

Using with /core:done

# Complete current task
/core:done

...