Pitfalls of Migrating Agent Tickets to GitHub
AlexKim · x · 2026-07-11
This post outlines two common pitfalls when migrating an agent ticketing system to GitHub Issues:
- gh api -f passes strings, but the subtask API expects integers; using the wrong parameter type will directly return a 422 error.
- Subtasks are linked by issue ID, not issue number; once a repository has history, these two will diverge.
The author also notes that github doesn't automatically assign the issue creator to themselves. Thus, if an agent relies on --assignee @me without explicitly assigning itself during subtask creation, the task will quietly "disappear" from the queue. The overall message: migrating from Linear to GitHub might look simple on the surface, but the real challenge lies in semantic differences, not just tweaking config files.
More from coding & agent
- A better path to agent autonomy is running waves, finding friction, and iterating — JnBrymn · 2026-07-22
- Coding agents are heading toward an AI-writes, AI-reviews, human-approves workflow — aftahi_ai · 2026-07-22
- oMLX 0.5.2 adds Mac menu-bar stats, low-bit decode kernels, and faster downloads — awnihannun · 2026-07-22
- GitHub review bot hits its PR limit and forces a 39-minute cooldown — DanielLockyer · 2026-07-22
- Max reasoning effort appears to be mobile-only in Codex Remote, not desktop — GabGarrett · 2026-07-22
- A Reddit demo argues online stores should expose carts and pricing through MCP — gelembjuk · 2026-07-22