dflydev/check-runs-action

✅ GitHub Check Runs Action

check-runs-action's Issues

Support checks on a different target

It could be useful to be able to submit check runs to a different repository / SHA, not just the current one.

Allow multiple independent conclusions for checks.

Currently, we can conclude multiple checks at once using:

      - uses: dflydev/check-runs-action@v1
        with:
          token: ${{ secrets.GITHUB_TOKEN }}
          conclusion: success

And we can even specify the checks that this should apply to, using JSON:

      - uses: dflydev/check-runs-action@v1
        with:
          token: ${{ secrets.GITHUB_TOKEN }}
          checks: [ { "id": "check-1", name: "Check 1" }, { "id": "check-2", name: "Check 2" } ]
          conclusion: success

But it is impossible to set individual conclusions for the different checks. It seems it would be simple enough:

      - uses: dflydev/check-runs-action@v1
        with:
          token: ${{ secrets.GITHUB_TOKEN }}
          checks: [ { "id": "check-1", name: "Check 1", conclusion: "success" }, { "id": "check-2", name: "Check 2", conclusion: "failure", output: { summary: "Meep" } } ]

But this is not currently permitted; and we get the odd message:

Error: invalid format for 'checks: SyntaxError: Unexpected token c in JSON at position 46

This forces us to duplicate the job countless times for each individual check, which is sloppy and a maintenance pain.

Ideally, the checks input would accept the full scope of a check's definition, as specified in https://github.com/dflydev/check-runs-action/blob/master/src/namespaces/Inputs.ts#L28-L42

Unable to process command '::set-env'

I get those error using check-runs-action

Run dflydev/[email protected]
  with:
    token: ***
    checks: [
    { "id": "build", "name": "Build Code" },
    { "id": "unitTests", "name": "Unit Tests" }
  ]
  
    status: queued
  env:
    JAVA_HOME: /opt/hostedtoolcache/Java_Adopt_jdk/8.0.292-1/x64

Error: Unable to process command '::set-env name=DFLYDEV_CHECK_RUN_COLLECTIONS,::{"collections":[{"collection":"default","checkRuns":[{"status":"queued","id":"build","name":"Build Code","gitHubCheckRunId":6813436470},{"status":"queued","id":"unitTests","name":"Unit Tests","gitHubCheckRunId":6813436622}]}]}' successfully.

Error: The `set-env` command is disabled. Please upgrade to using Environment Files or opt into unsecure command execution by setting the `ACTIONS_ALLOW_UNSECURE_COMMANDS` environment variable to `true`. For more information see: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/

Since https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/ maybe the code need to be adapted ?