github-script | Write workflows scripting the GitHub API in JavaScript | Continous Integration library

I have been trying to understand how to get a multi-line comment written to a PR using github actions. I was trying to use github.rest.issues.createComment() as shown in Commenting a pull request... and then handling the multi-line issue by using an environmement variable as shown here: workflow commands. Ultimate goal is to take some multi-line output stdout from a python script (or a log file) and place that as a comment back to the PR that the workflow is running on. The yml file below runs fine up until the last step where I try to access the environment variable I created and use it as the body of the createComment(). The environment variable is created and appears to be available but fails when I try to use it for the body of the comment. Error from github actions is below the code. If I add quotes like body: "${{env.SCRIPT_OUTPUT}}" then I get same error. I would like to use createComment() if possible, I know there is a create comment from Peter Evans that I will likely try next but trying to understand why this is not working.

This is what I am trying:

I need to create a YAML job that checks if a milestone is set on a PR and fail an automated check if there is no milestone set.

This is the job that I have in the .yml file:

I have a project with Github Actions that implements multiple workflows that can be triggered by a single push event (depending on path filter).

So a push with a single commit can trigger multiple workflows, so far so good.

In each workflow I am running actions/github-script to create dynamic run-checks with the following step:

Let's take this example composite action found on Github's documentation:

Let's take as an example this workflow with two jobs - build and comment:

I am trying to build a GitHub workflow that performs simple pre-commit checks whenever a PR is created into a certain repository and triggers a message if some check has failed. The problem is that I want that message to be as specific as possible and, therefore, the message has to contain the error that is preventing the check to succeed. To perform the pre-commit check I am using pre-commit action and, to automate the messages, I am using the official actions github-script.

Since I am utilizing the pre-commit action to perform the checks, I think I am not able to use the set-output solution to define the outputs of the step that is validating for the errors and reference those outputs later in my error message. Is there any other way to workaround this problem?

Here is an excerpt of my workflow pipeline:

I have a step in a github workflow job that looks like this:

I'm using github-script for GitHub actions, which allows you to easily access GitHub API. I'm trying to check if an issue has not been closed by clicking on the "close button", that is, via a commit or via merging a pull request that includes a closing commit (or closes in the PR body). However, there does not seem an easy way to do that. This is the event information the GitHub API returns:

• If the issue has been closed from a commit, it adds the commit_id
• If the issue has been closed from GitHub app (this does not include the web, apparently), performed_via_github_app is set to non-null.

However, there does not seem to be a special way to signal an issue has been closed by a pull request, apparently. Or is it?