actions-runtime

Standardize GitHub Action entry points with Effect by wrapping your pre, main, and post scripts in a unified Action.run call. This provides a type-safe runtime that manages process lifecycle, environment configuration, and error reporting consistently.

Handle GitHub Action state and secret masking in TypeScript by using curated ActionServices that expose platform capabilities like logging and state management. This ensures consistent secret masking and shared state via GITHUB_STATE without manual boilerplate.

GitHub Actions swallow defects in workflow logs when error handling is inconsistent across entry points. Using a standardized runtime wrapper ensures proper error rendering and avoids swallowing defects by enforcing consistent error handling.

Yes, you can use a memoized layer architecture for GitHub Actions runtime. It integrates NodeServices and custom ActionServices to satisfy type-safe wiring requirements, ensuring proper service composition and environment configuration.

The best way to manage GitHub Action lifecycle and exit codes is to use a standardized runtime that wraps your program. It ensures proper process exit codes, lifecycle management, and error rendering across pre, main, and post scripts.