v0.10.0

GitHub: pull requests and commits that name an issue link to it and move it along. Also display
options in saved views. Updating a self-hosted copy applies two migrations in each workspace's
database, which run on their own; there is no D1 migration and no new setting. The protocol goes
to version 14, so open tabs reload and sync again. (#88, #89)

Added

• GitHub connections. An admin adds one in Settings, GitHub, and sets it as a webhook on a
  repository or an organization. Pull requests link the issues their branch, title or
  description names, and the issue page lists them with their state. A draft moves its issues to
  In Progress and an open pull request to In Review. A merge moves the issues it fixes, named by
  its branch or after "Fixes", "Closes" or "Resolves", to Done, as does a commit to the default
  branch that says so. Track never moves an issue back, nor out of Done or Canceled, and each
  move's activity links the pull request or commit. The issue page copies a branch name for the
  issue, the inbox and webhooks name GitHub as the actor, and MCP's get_issue lists an issue's
  pull requests. The public demo takes no deliveries. (#89)
• Display options. A Display menu groups the list and the board by status, priority, assignee,
  project or nothing, orders them by hand, priority, due date, last update or creation, and
  picks the properties rows and cards show. The options live in the page's URL and in saved
  views, so everyone opening a view sees the same page. Dragging an issue into another group
  sets that field. (#88)

Changed

• The table's columns and sort follow the page's URL and saved views instead of one browser's
  storage, so columns hidden before this version show again. (#88)