github-script

Best practices for github-script actions dictate using @actions/core for logging, inputs, and outputs, while avoiding console logs to ensure deterministic workflow execution and maintainable code.

The best way to handle logging and outputs in github-script actions is to prescribe core.info for logging, core.setOutput for outputs, and core.getInput for inputs, avoiding console logs entirely.

To get inputs and set outputs in GitHub Actions JavaScript, use core.getInput to read workflow inputs and core.setOutput to export results, ensuring proper data propagation through deterministic workflows.

Yes, github-script supports TypeScript projects and linting. The guidelines include tooling considerations, typechecking, and error handling patterns to ensure safe and maintainable TypeScript workflows.

You should avoid console logs in GitHub Actions JavaScript because they bypass the Actions toolkit. Using core.info ensures proper integration with GitHub Actions infrastructure and consistent error handling.

A limitation of github-script is that it requires strict adherence to @actions/core and @actions/github patterns. Improper error handling or using console logs can break deterministic workflow execution and data propagation.