Skip to content

chore: track issues in Linear; put synced GitHub issues into its cloudpid project - #749

Merged
ian-pascoe merged 2 commits into
mainfrom
chore/linear-issue-tracker
Nov 11, 2026
Merged

ian-pascoe merged 2 commits into
mainfrom
chore/linear-issue-tracker

Conversation

@ian-pascoe

Copy link
Copy Markdown
Owner

Summary

Issues now live in Linear (team SPI, project cloudpid), as in commissary (spiritledsoftware/commissary#454). GitHub Issues stay the public intake, including cloudpid-report issues from the GitHub App.

sequenceDiagram
    participant GH as GitHub issue
    participant Sync as Linear GitHub sync
    participant WF as linear project workflow
    participant L as Linear (SPI)
    GH->>Sync: issues.opened
    Sync->>L: copy into SPI, no project
    GH->>WF: issues.opened
    WF->>L: wait for the synced copy, set project cloudpid (unless it has one)
Loading
 AGENTS.md                              # issue tracker pointer → Linear
 docs/agents/issue-tracker.md           # gh → Executor Linear app / linear CLI
 docs/agents/triage-labels.md           # + Linear label ids
 docs/development/infra.md              # + linear project workflow, LINEAR_API_KEY
+.github/workflows/linear-project.yml
+scripts/linear-project.sh              # ported from commissary's tools/linear-project.sh

Evidence

Merge Danger

Door: two-way

Blast Radius: agents

Changes where agents read and write issues; no runtime code. The workflow only sets a project on a synced issue that has none.

…dpid project

The engineering skills track issues in Linear (team SPI, project cloudpid), reached
through Executor's Linear app with the linear CLI as fallback; GitHub Issues stay the
public intake, synced one-way into Linear. The new workflow linear project puts each
synced GitHub issue's copy into project cloudpid (repository secret LINEAR_API_KEY).
@ian-pascoe

Copy link
Copy Markdown
Owner Author

Review report: b9c0d8ffad8ccca63f7956f17c15b641555f8090

code-review against origin/main (Standards + Spec). No blockers.

Fixed:

  • infra.md: the linear project note now sits apart from ci.yml's job list, and its secret pointer goes to the LINEAR_API_KEY bullet.
  • issue-tracker.md: when no Linear issue carries a GitHub number, try gh pr view <n> (issues and PRs share numbers).

Advisory, left as is:

  • AGENTS.md's pointer repeats "Executor, falling back to the linear CLI"; kept identical to commissary's.
  • LINEAR_PROJECT id appears in both the workflow and issue-tracker.md; ids are cached in docs to save agents a lookup, as in commissary.
  • scripts/linear-project.sh smells (global deadline/issue, JSON re-parsed with jq): kept byte-identical to commissary's so the two stay in step.
  • Lowercase workflow name linear project: matches commissary.
  • Unverified: Linear's GitHub sync is assumed to copy GitHub labels (needs-triage, cloudpid-report) onto the Linear copy; the first new issue will show it.

@ian-pascoe
ian-pascoe merged commit 32e8081 into main Nov 11, 2026
30 of 32 checks passed
@ian-pascoe
ian-pascoe deleted the chore/linear-issue-tracker branch November 11, 2026 16:48

This branch was successfully deployed

1 active deployment
preview — b9c0d8ff Deployed Nov 11, 2026 by ian-pascoe via Preview #1374
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