Skip to content

--affected failing to resolve main even on full checkout #9320

@chris-olszewski

Description

@chris-olszewski

Verify canary release

  • I verified that the issue exists in the latest Turborepo canary release.

Link to code that reproduces this issue

https://github.com/amannn/next-intl

What package manager are you using / does the bug impact?

pnpm

What operating system are you using?

Linux

Which canary version will you have in your reproduction?

2.2.3

Describe the Bug

Using --affected results in the following log line:

Failed to resolve base ref 'main' from GitHub Actions event: git error: fatal: ambiguous argument 'main': unknown revision or path not in the working tree.

example in GH Actions

Expected Behavior

We shouldn't have get an ambiguous argument when testing out main. Especially with fetch-depth: 0

To Reproduce

See next-intl attempting to use --affected: example job

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind: bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions