project-flow-ops

Triage GitHub issues and PRs with Linear tasks by cross-system mapping items into a unified execution flow, classifying work into merge, port, close, or park, and creating internal Linear items with public GitHub updates.

Keeping GitHub backlog visibility while tracking work in Linear involves mapping GitHub issues to internal Linear tasks, ensuring public GitHub status updates while internal execution remains intact for clear backlog clarity.

Deciding whether an issue belongs in GitHub or Linear depends on triage classification: merge, port, close, or park, determining when to create or update Linear items while keeping public GitHub visibility.

Linking GitHub pull requests to Linear tasks for backlog grooming is supported by cross-system mapping, which aligns public PR status with internal Linear progression to reduce tracking gaps.

Limitations of coordinating workflow across GitHub and Linear include potential public-private alignment gaps, requiring consistent triage decisions to classify items as merge, port, close, or park to maintain execution flow.