project-flow-ops

To coordinate GitHub and Linear for backlog triage, link public GitHub work to internal Linear lanes to establish a unified execution flow. This synchronizes status across both platforms and enforces public-private state governance rules.

Deciding if work belongs in Linear versus GitHub involves applying governance rules that keep GitHub public-facing while Linear acts as the internal execution layer. This classification guides whether items merge, port, close, or park.

To synchronize GitHub resolutions when work ships or is blocked, apply cross-repo planning rules that flow status updates back to GitHub from Linear. This ensures the public GitHub surface remains accurate during execution.

Yes, you can triage open pull requests across multiple repositories using Linear by mapping active items to Linear lanes. This cross-repo planning establishes a synchronized execution flow and links public PRs to internal tasks.

You should avoid GitHub and Linear synchronization if your project lacks a clear public-private boundary. The system relies on GitHub remaining public-facing while Linear serves strictly as the internal execution layer.