What the HELL have i DONE

Integrations

GitHub Integration

Connect your GitHub account to sync issues with board cards — import open issues, create issues from cards, and keep everything in sync.

Setup
3 steps
Sync
2-way
Accounts
Multi

What you can do

Import issues

Pull open GitHub issues into your board as cards in one click.

Create from cards

Open a card and spin up a new GitHub issue or link an existing one.

Bi-directional sync

Keep issue status and card position aligned across both systems.

How it connects

Account

OAuth connect

Repository

Linked to board

Board

Kanban workspace

Sync

Cards ↔ issues

Using the hosted app?

GitHub OAuth is already configured at whatthehellhaveidone.net. Skip the self-hosting setup below and jump straight to Connect your account.

Self-hosting — GitHub OAuth App

2

Set the callback URL

3

Copy credentials

4

Add to your .env

5

Reload config

Connect your GitHub account

1

Open Integrations

2

Authorize on GitHub

3

Add more accounts (optional)

Link a repository to a board

1

Open board settings

2

Select a repository

3

Connect

Working with issues

Import GitHub issues as cards
Create a GitHub issue from a card

Workflow automation

Read the full GitHub + board workflow guide →

1

Create issues when work starts

2

Choose who works on it

3

Move pull requests into review automatically

Reference the issue in your pull request

Mention the linked issue in the PR title or body with Fixes #12 or #12. The app moves the card automatically, and Copilot review is requested only when the card was assigned to Copilot on move.

Sync direction

Two-way sync

Changes in GitHub reflect on the board and vice versa when webhooks are configured on the repository.

Import only

Pull issues into the board without pushing card changes back to GitHub.

Webhook setup (two-way sync)

For GitHub → board updates, add a repository webhook with this payload URL:

https://your-domain.com/webhooks/github

Connecting a repository registers this webhook for issues and pull_request events. GitHub must be able to reach your app over HTTPS.

See GitHub's webhook documentation for event types, secrets, and delivery settings.

Local testing checklist

  1. Set APP_URL to your public tunnel URL, not localhost.
  2. Expose the app over HTTPS with a tunnel such as ngrok http https://whatthehellhaveidone.test or Herd Share.
  3. Run php artisan queue:work so webhook jobs can process deliveries.
  4. Reconnect the repository in board settings so GitHub picks up the refreshed webhook URL.

Ready to connect?

Open integrations

Next steps