Nx Cloud Run Details (gh bot) not working

[cyrus-za]

Current Behavior

Run details do not work (after adding repo access and adding the env to github actions. Using MansaGroup/nrwl-nx-actions

Expected Behavior

I expect the github bot to show run details in my PRs

Steps to Reproduce

1. Run yarn create-nx-workspace
2. Push to a new github repo
3. Add the below code to .github/workflow/nx.yml
4. Add https://github.com/apps/nx-cloud to your repo
5. Open a PR of some code changes
6. Nothing happens

Failure Logs

No logs at all

Environment

Using Github actions

nx.yml file

name: Run NX Jobs
on:
  pull_request:
    branches: [master]

jobs:
  build:
    runs-on: ubuntu-latest

    env:
      NX_CLOUD_AUTH_TOKEN: ${{ secrets.NX_CLOUD_AUTH_TOKEN }}
      NX_BRANCH: ${{ github.event.number }}
      NX_RUN_GROUP: ${{ github.run_id }}

    steps:
      - uses: actions/checkout@v2
        with:
          ref: ${{ github.event.pull_request.head.ref }}
          fetch-depth: 0

      - uses: actions/setup-node@v2
        with:
          node-version: 12

      - name: install dependencies
        run: yarn install --frozen-lockfile

      - name: Fetch other branches
        run: git fetch --no-tags --prune --depth=5 origin $GITHUB_BASE_REF

      - name: Nx
        uses: MansaGroup/nrwl-nx-action@v2.0.3
        with:
          targets: lint,build,test,e2e

[cyrus-za]

@vsavkin any idea?

[rarmatei]

Hey there! I tried out your example workflow in this repository and it seems to work.

The workflow file should be identical to yours: https://github.com/rarmatei/test-gh-issue1/blob/main/.github/workflows/nx.yml (I'm using main instead of master and I'm grabbing the Cloud auth token from nx.json of the env var)

I'm not sure if it was just a typo, but I did have to change the workflow file location from .github/workflow/nx.yml --> .github/workflows/nx.yml (otherwise the GH Action checks won't even start)

I'll close this for now, but if you have another repro scenario we can try, I'll be happy to help!

[github-actions]

This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context.