temporary-id-safe-output

You can use temporary ID support to generate short-lived placeholder IDs for GitHub issues, which dynamically resolve to actual issue numbers at execution time. This bridges the gap in agentic workflows so newly created issues can be immediately referenced.

Temporary IDs in CI/CD pipelines are unique, short-lived identifiers for issues created during a workflow run. You need them when an agent must create a parent issue and immediately link sub-issues to it before the actual GitHub issue number is known.

Dynamic resolution resolves placeholder IDs to actual GitHub issue numbers at execution time. This cross-job communication mechanism ensures links between issues are correctly established even when dependencies are not yet assigned a permanent number.

Yes, temporary IDs facilitate cross-job communication within GitHub Actions by resolving placeholder identifiers to actual issue numbers. This enables immediate inter-issue referencing in CI/CD pipelines without waiting for sequential assignment.

Linking sub-issues fails because the parent issue number is not yet known during simultaneous creation. Temporary ID support addresses this by assigning a short-lived ID that dynamically resolves to the actual number at execution time.

Temporary IDs are short-lived and designed specifically for resolving placeholder references to actual GitHub issue numbers within a single workflow run. They should not be used for permanent tracking or outside the scope of immediate inter-issue referencing.