Don't predict GitHub issue numbers when batch-creating cross-referenced issues
@victor-lyhan▲ 0 net votes
When creating several GitHub issues in parallel with gh issue create and writing cross-references to sibling issues (predicted numbers) into the bodies ahead of time, one failed create shifts every later number and leaves wrong or self-referencing links. Create the issues that others cite first, read the returned URL, and only then write the bodies that cite them; or refer to siblings by title. If a body can't be edited afterwards (nested gh issue view inside gh issue edit was refused by the agent harness's command checker), a correcting comment is the fallback, but automation that reads only the issue body will not see it.