Tasks board: first-class GitHub Issues provider (gh-auth, per-repo)#58
Closed
Legacynnn wants to merge 22 commits into
Closed
Tasks board: first-class GitHub Issues provider (gh-auth, per-repo)#58Legacynnn wants to merge 22 commits into
Legacynnn wants to merge 22 commits into
Conversation
Snapshot of the in-progress Linear tasks/integrations feature and the GitHub-issues board design doc + implementation plan, committed as a clean baseline before layering the GitHub provider work on top.
…lback, JSON round-trip
…es, create/update via GraphQL
… labels/assignees, honor create status
…s (file-size rule)
Owner
Author
|
Closing as superseded — already merged into Every commit in this PR was relanded on The merge conflicts were all |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Makes GitHub issues a first-class, natively-editable provider on the Tasks board (previously Linear-only), scoped per-repository and authed through the bundled
ghCLI. This is the board-first half of the design (spec Phases 1–3); the context-sidebar work (Linear-in-sidebar + GitHub-issue inbox rebuild) is a planned Phase 4 follow-up.What changed
Backend — multi-provider integrations layer
integrationsbackend behind aTaskProvidertrait +resolve_providerdispatch; Linear is now one impl, GitHub the other. Every IPC command routes through the trait (no behavior change for Linear).integrations/github/client over the existingforge::githubgh-auth + GraphQL plumbing (one canonical GitHub auth path): repos-as-teams, issue listing, labels/assignees, create/update — split intoclient/map/ops/queries/responsesmodules.Valuereads index through the{data}envelope; post-mutation reloads use an uncached path (avoids a stale-read-after-edit bug); repo labels/assignees are fully paginated;create_issuehonors the target column.ghlogin resolution avoids a per-account profile network fan-out and is deterministic.list_task_labels/list_task_assigneesin the companion dispatch (pre-existing gap surfaced by tests).Frontend — GitHub on the board
IntegrationProvider = "linear" | "github"; provider tab enabled; board driven by persisted provider state.Test plan
cargo clippy --all-targets -D warningsclean.editor/terminalare pre-existing on the base branch, unrelated.)gh-authed env): connect GitHub → pick repo → Sync → verify columns, drag open↔closed, inline edits, create, agent-review, start-workspace; confirm Linear tab unchanged.🤖 Generated with Claude Code