New action triggering as unknown event - unnamed workflow by ghost instead of adding this into the same action result

Getting an issue while executing Github action, it creates a new action named unknown event - unnamed workflow by ghost instead of adding this into the same action result. [See screenshots below]

This is my .yml file and its triggering through Jest Github Action Reporter

name: Pull Requests CI

on: [pull_request]

jobs:
test:
name: Test
runs-on: ubuntu-latest
strategy:
matrix:
service: [
β€” All services goes here
]

steps:

  • name: Check if service has changed
    uses: actions/github-script@0.9.0
    id: service-changed
    with:
    result-encoding: string
    script: |
    ### Logic part here

  • uses: actions/checkout@v2

    Logic part here

  • name: Setup Node
    β€” Logic part here

  • name: Login to npm repo
    β€” Logic part here

  • name: Yarn Install
    β€” Logic part here

  • name: Lint and Prettify
    β€” Logic part here

  • name: Build
    β€” Logic part here

  • name: Yarn Test
    β€” Logic part here

  • name: Yarn E2E
    β€” Logic part here

  • name: Jest Github Action Reporter
    uses: IgnusG/jest-report-action@v2.3.2
    if: {{ steps.service-changed.outputs.result == 'true' && (success() || steps.unit-test.outcome == 'failure' || steps.e2e-test.outcome == 'failure') }} with: working-directory: {{ matrix.service.dir }}
    access-token: ${{ secrets.GITHUB_TOKEN }}
    run-name: test
    check-name: Test

Hi @fahadshehzada,

This issue has popped up a few times now for various actions. The issue is that the action you are using creates a check run with annotations on the commit SHA used by the workflow. However in a workflow triggered via a pull request this is actually a merge commit that doesn’t exist outside of the workflow.

I have added a comment with a fix to the issue you made over at the IgnusG/jest-report-action repository.

2 Likes

Thanks for the fix. Really appreciated the solution

My issue is resolved now