Repository navigation
chore: track issues in Linear; put synced GitHub issues into its cloudpid project - #749
Merged
Merged
Conversation
…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).
Owner
Author
Review report:
|
This branch was successfully deployed
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
Issues now live in Linear (team SPI, project cloudpid), as in commissary (spiritledsoftware/commissary#454). GitHub Issues stay the public intake, including
cloudpid-reportissues 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)Evidence
actionlint,shellcheck,oxfmtclean.vi.waitForin apps/server tests #745 (already synced as SPI-576):SPI-576 is already in project cloudpid; kept.(exit 0)LINEAR_API_KEYis set.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.