GitHub + Board Workflow
This page summarizes the GitHub-connected sprint workflow: issue creation on move, assign-on-move (Copilot or team member), and automatic Review column movement with optional Copilot PR review.
The same content also lives in the repository root as
GITHUB-BOARD-WORKFLOW.md for sharing outside the app.What we built
| Step | What happens |
|---|---|
| Move to In Progress | Creates a linked GitHub issue and prompts for who should work on it |
| Assign on move | Choose GitHub Copilot or a board team member |
| Open a pull request | Card moves to Review when the PR references the issue |
| Copilot review | Requested automatically only if the card was assigned to Copilot on move |
One-time board setup
- Settings → Integrations — connect GitHub.
- Board Settings → connect the repository.
- In Progress column (⋯) → Create GitHub issue.
- Board settings → Pull request automation → target Review.
- Add board members (non-viewer) for the team picker.
Per card
Move to In Progress
Drag the card or use the move controls.
Choose who works on it
Copilot, a team member, or skip for now.
Open a PR
Use Fixes #123 or #123 in the title or body.
Review column
Card moves automatically; Copilot review only if you picked Copilot.
Copilot vs team member
| GitHub Copilot | Team member | |
|---|---|---|
| Board assignee | Cleared | Set on the card |
| GitHub issue assignee | Copilot agent | Not set by the app |
| Auto Copilot PR review | Yes | No |
| Moves to Review on PR | Yes | Yes |
Local testing
GitHub webhooks require HTTPS. Run php artisan queue:work, tunnel the app, set APP_URL, then reconnect the repository in board settings.
Not included yet
- Human as GitHub issue assignee
- Project invitees who are not board members
- Live board refresh when webhooks move cards