@Plysepter ah, thank you! That definitely helped. Here’s my current best working config:

name: Node.js CI

on:
  push:
    branches: [ master ]
  pull_request:
    branches: [ master ]

jobs:
  build:

    runs-on: ubuntu-latest

    strategy:
      matrix:
        node-version: [10.x, 12.x]

    steps:
    - uses: actions/checkout@v2
      with:
        ref: ${{ github.event.pull_request.head.ref }}
        fetch-depth: 0
    - name: Use Node.js ${{ matrix.node-version }}
      uses: actions/setup-node@v1
      with:
        node-version: ${{ matrix.node-version }}
    - run: git fetch --no-tags --prune --depth=5 origin master
    - run: yarn install --frozen-lockfile
    - run: yarn affected:build --base=origin/master
      env:
        CI: true

I think this issue can be closed now.

I run affected:build like this:

npm run affected:build -- --base=$NX_BASE

where NX_BASE is different depending on whether a push event or a pull request triggers the workflow.

In case of a push, we want to look at the commit id of the second newest commit, which translates to export NX_BASE=$(git rev-parse HEAD~1)

Keep in mind that you need to use the checkout action earlier with a fetch depth of at least 2 for this to work. - uses: actions/checkout@v2 with: fetch-depth: 2

In case of a pull request, it could look like something like this export NX_BASE_TEMP=$(git log --format=%H -n 1 origin/${{ github.base_ref }})

This is the newest commit id of the target branch. I needed to use git fetch origin beforehand for this to work.

Hope this helps a bit!

So I encountered this issue in Github Actions and after some debugging I have found the following:

By default Github Actions checkout action only pulls the latest commit in a detached head state. I have found this causes any git operation for comparison to break.

I resolved the issue in Github Actions with these steps:

- uses: actions/checkout@v2
  with:
      ref: ${{ github.event.pull_request.head.ref }}
      fetch-depth: 0
- run: |
       git fetch --no-tags --prune --depth=5 origin master

The key here is changing the default ref so that it pulls the branch instead of just the single commit. I am comparing for a PR so I am only fetching master and the depth flag could be adjusted/removed for different use cases and you could fetch as many branches as your use case needs.

- name: Lint affected projects
  run: ./node_modules/.bin/nx affected --target=lint --base=origin/master --head=HEAD --parallel --maxParallel=2

To make this work I had to ensure I had origin/master instead of just master for the base flag even though the master branch was pulled. I don’t have an exact explanation as to why but this did allow my lint, format and testing jobs to succeed.

I hope this can be of use to others experiencing this issue

Also link to github checkout action thread regarding this use case: https://github.com/actions/checkout/pull/155 (edit: improved formatting, added link to thread)

same situation, nothing works

@DedoxBR I resolved this by replacing above command with nx affected:apps --base=origin/master --head=origin/master --plain Ref:

Is there anything new? Having the same problem. Having a default branch “develop” and trying to test and build affected with GitHub Actions, but no matter what i set as base head or anything else helps. Always getting “Not a valid object name xxx”

are you sure you aren’t forgetting the double dash?

WORKS npm run affected:apps -- --base develop vs

DOESN’T WORK npm run affected:apps --base develop

@DedoxBR I resolved this by replacing above command with nx affected:apps --base=origin/master --head=origin/master --plain Ref:

@whimzyLive it didn’t work for me.

If it helps, I created a clean repository simulating the problem here: https://github.com/andrebraghini/nx-affected-test

I have the same problem on CI using Github Actions and it only happens when running on a branch other than master.

When running on the master it works without problems.

@DedoxBR I resolved this by replacing above command with nx affected:apps --base=origin/master --head=origin/master --plain Ref:

Tnx. works for me, so locally I had branch accessible with branch=x but on CI it should be branch=origin/x

Hi, do you have a master branch checked out locally?

If master is not your default branch, you should set --base to your default branch:

For Example:

npm run affected:apps -- --plain --base develop