Skip to content

feat(tracker): add GitHub issues support - #1

Draft
kmatsunami wants to merge 2 commits into
mainfrom
codex/github-tracker
Draft

feat(tracker): add GitHub issues support#1
kmatsunami wants to merge 2 commits into
mainfrom
codex/github-tracker

Conversation

@kmatsunami

Copy link
Copy Markdown
Owner

Context

This fork needs Symphony to read and reconcile GitHub Issues instead of depending on Linear.

TL;DR

Add a GitHub tracker profile and switch the default workflow/docs to it while keeping Linear compatibility.

Summary

  • add a GitHub Issues client/adapter and a shared tracker issue model
  • expose github_rest and wire config, dashboard, and workspace cleanup to the GitHub profile
  • update the default workflow, docs, skills, and tests for GitHub-backed orchestration

Alternatives

  • keep Symphony Linear-only and handle GitHub only inside the agent workflow; rejected because the orchestrator still could not poll, reconcile, or clean up GitHub issues

Test Plan

  • make -C elixir all
  • targeted GitHub tracker and workspace cleanup regressions are covered by the Elixir test suite

Add a GitHub Issues-backed tracker adapter alongside the existing Linear integration and switch the fork's default workflow and docs to the GitHub profile.

This adds the github_rest dynamic tool, normalizes tracker issues into a shared issue model, and updates tests and repo tooling for the new profile.
Batch open issue state refreshes so the orchestrator does not issue one
GET per running ticket on every poll.

Wrap github_rest responses with status, headers, and body so agents can
follow pagination links when reading long comment threads.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant