GitHub Integration

Push agent specifications as GitHub Issues for Copilot Agent to implement with full product context

GitHub Integration Overview

The GitHub integration lets you push agent specifications as GitHub Issues. When combined with GitHub Copilot coding agent, issues created from Delvyn Studio include full product context — vision, strategy, guardrails, and acceptance criteria — so the AI agent implements exactly what you need. You can also link existing GitHub issues to product strategy items, objectives, and discovery projects.

Agent Spec Push

  • • Push specs as structured GitHub Issues
  • • Copilot Agent picks up and implements
  • • Full product context included
  • • Track push history and linked PRs

Issue Linking

  • • Link issues to strategy initiatives
  • • Connect to OKR objectives
  • • Track discovery project issues
  • • Sync issue status updates
Prerequisites

Before You Begin

  • • You need admin access to your GitHub repository or organization
  • • Your GitHub repository must be accessible (public or private with permissions)
  • • You'll need to create a GitHub Personal Access Token or GitHub App
  • • Ensure your Delvyn Studio plan supports integrations
Step 1: Create GitHub Personal Access Token

Generate Personal Access Token

  1. 1

    Go to GitHub Settings

    Navigate to GitHub → Settings → Developer settings → Personal access tokens → Tokens (classic)

  2. 2

    Generate New Token

    Click "Generate new token (classic)" and provide a descriptive note (e.g., "Delvyn Studio Integration")

  3. 3

    Select Required Scopes

    Enable the following scope:

    • repo - Full repository access (required for issue management)
  4. 4

    Copy the Token

    Save this token securely - you'll need it for the Delvyn Studio configuration

Token Format

Your GitHub Personal Access Token should look like:

ghp_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Step 2: Configure Delvyn Studio
  1. 1

    Navigate to Integrations

    Go to Settings → Integrations in your Delvyn Studio workspace

  2. 2

    Enable GitHub Integration

    Click on the GitHub tab and toggle "Enable GitHub Integration" to ON

  3. 3

    Enter Personal Access Token

    Paste your GitHub Personal Access Token in the "Personal Access Token" field

  4. 4

    Test Connection

    Click "Test Connection" to verify your configuration and load available repositories

  5. 5

    Select Default Repository

    Choose a default repository from the dropdown for creating new issues

  6. 6

    Optional: Set Up Webhooks

    For automatic status updates when issues or pull requests are closed, expand the "Webhook Configuration" section and follow the step-by-step guide to add a webhook to each GitHub repository you want to track.

  7. 7

    Save Configuration

    Click "Save Settings" to activate the integration

Configuration Fields

Personal Access Token: Your GitHub token (ghp_xxx...)

Default Repository: Chosen from your accessible repositories

Webhook Configuration: Generate a secret and add webhooks to your repositories for automatic status updates

Pushing Agent Specifications

Agent Spec Push Workflow

The primary use case for the GitHub integration is pushing agent specifications as structured GitHub Issues. Here's how it works with Copilot Agent:

  1. 1

    Generate Agent Specification

    From an idea, discovery insight, or key result — Delvyn Studio generates a structured spec with product context

  2. 2

    AI Coach Review

    The AI product coach checks the spec for clarity, completeness, and alignment with vision and strategy

  3. 3

    Push to GitHub

    Select "Push to GitHub" and choose the target repository — a structured GitHub Issue is created

  4. 4

    Copilot Agent Implements

    Assign the issue to Copilot Agent — it reads the full product context and implements the feature

What's Included in the Issue

Title and description derived from the agent spec

Product vision and strategic context

Acceptance criteria from the spec

Strategic guardrails (anti-goals, boundaries, UX principles)

Labels for categorization

Linking Existing Issues

You can also link existing GitHub issues to items in Delvyn Studio for traceability:

Product Strategy

Link development tasks to strategic initiatives and track implementation progress.

OKR Objectives

Connect feature development to objectives and key results for better alignment.

Discovery Projects

Link technical research and prototyping issues to discovery projects.

How to Link Issues

  1. 1. Open the item you want to link (strategy, objective, etc.)
  2. 2. Look for the "Linked Issues" or "GitHub Issues" section
  3. 3. Click "Link GitHub Issue" or the "+" button
  4. 4. Search for or enter the GitHub issue number (e.g., #123)
  5. 5. Select the issue and click "Link"

Status Synchronization

The integration automatically syncs issue status updates between GitHub and Delvyn Studio:

Open
In Progress
In Review
Closed
Troubleshooting

Common Issues

Authentication Failed

  • • Verify your GitHub URL is correct
  • • Check that your Personal Access Token hasn't expired
  • • Ensure your token has the required scopes
  • • Verify your username is correct

Issues Not Syncing

  • • Check the integration status in Settings → Integrations
  • • Verify the linked issue exists and is accessible
  • • Review sync logs for error messages
  • • Try unlinking and re-linking the issue

Permission Errors

  • • Ensure your token has "repo" scope for private repositories
  • • Check that you have access to the specified repository
  • • Verify your GitHub App has the correct permissions
  • • Contact your repository administrator if needed

Rate Limiting

  • • GitHub API has rate limits (5,000 requests/hour for authenticated users)
  • • Large repositories may hit rate limits during initial sync
  • • Consider using a GitHub App for higher rate limits
  • • Sync may be temporarily paused if limits are exceeded

Need Help?

If you're still experiencing issues, please contact our support team with:

  • • Your GitHub setup type (Personal Access Token or GitHub App)
  • • Error messages from the integration logs
  • • Screenshots of your configuration
  • • The specific repository you're trying to connect