CRE-1330

[mchain0]

CRE-1330

[github-actions]

✅ API Diff Results - No breaking changes

---

📄 View full apidiff report

[jmank88]

@chainchad Do we need to configure the linter differently to handle --only-new-issues correctly?

[chainchad]

@chainchad Do we need to configure the linter differently to handle --only-new-issues correctly?

The default behavior for the upstream composite action is to use this flag if that's what you mean: https://github.com/smartcontractkit/.github/blob/main/actions/ci-lint-go/action.yml#L67-L70

[jmank88]

@chainchad Do we need to configure the linter differently to handle --only-new-issues correctly?

The default behavior for the upstream composite action is to use this flag if that's what you mean: smartcontractkit/.github@main/actions/ci-lint-go/action.yml#L67-L70

But why did we pass on the PR, but fail in the queue?

level=warning msg="[runner] Can't process results by diff processor: can't prepare diff by revgrep: could not read git repo: error executing \"git diff --color=never --no-ext-diff --default-prefix --relative 58a50811fe85b393f13288164645e210cdf07f7d --\": exit status 128: fatal: bad object 58a50811fe85b393f13288164645e210cdf07f7d\n"