temporary-id-safe-output

Temporary IDs let you reference newly created issues within the same GitHub Actions run before actual numbers are available. You assign a temporary ID to a parent issue, link sub-issues to it, and resolve the temporary ID to the real issue number at runtime via a shared map.

Yes, you can pass temporary IDs between jobs in GitHub Actions safely. The workflow uses error-safe handling and dynamic needs to propagate IDs through environments, ensuring unresolved IDs are reported without causing the entire workflow run to fail.

Cross-job issue tracking uses a shared map and environment variables to coordinate producer and consumer jobs. A producer job creates the issue and stores the temporary ID, while consumer jobs dynamically resolve these IDs to actual issue numbers during the same run.

No external dependencies are required to resolve temporary IDs within GitHub Actions. The resolution mechanism relies entirely on built-in workflow features, utilizing a shared map and runtime environment variables for localized, secure ID tracking.

The best way to dynamically link sub-issues is using temporary IDs. Create a parent issue with a temporary ID, immediately attach sub-issues referencing that temp ID, and let the runtime environment resolve the temporary ID to the actual issue number.

Workflows often fail because standard job dependencies expect resolved values immediately. Using error-safe temporary ID handling reports unresolved IDs gracefully and uses dynamic needs, preventing workflow failures while actual issue numbers are still pending.