project-flow-ops

To coordinate GitHub and Linear, triage open PRs and issues to decide what stays public versus moves into Linear for internal tracking. Link active GitHub work to Linear tasks to preserve execution context and synchronize public state with internal planning.

Keep an issue on GitHub when it belongs on the public-facing surface, and move it to Linear when it requires internal execution tracking. Triage open PRs and issues to classify whether work needs internal planning or should remain visible to the public.

Triage pull requests by classifying each one into governance categories like merge, port/rebuild, close, or park. This guides whether to create or update Linear items and reflects the public GitHub status in Linear for cross-team coordination.

Yes, you can use Linear as the internal execution layer while keeping GitHub public-facing. Audit and synchronize public GitHub state with internal Linear planning to align the public surface with internal execution lanes for better coordination.

The best way to link active GitHub work to Linear is by triaging open PRs and linking relevant GitHub issues to Linear tasks. This establishes the execution flow and preserves context across multiple repos by reflecting GitHub status in Linear.

PR classification enforces governance by categorizing pull requests as merge, port/rebuild, close, or park. It guides when to create or update Linear items and determines how to reflect the public GitHub status within Linear's internal execution lanes.