Cory Miller

Hey @voxpelli I've updated your branch with the `actions/checkout@v4` changes. I was not able to run the CI against this since the fork was behind. I've opened a PR in...

Some background: On Windows we found that `actions/checkout` did not respect the Windows [FileShare](https://learn.microsoft.com/en-us/dotnet/api/system.io.fileshare?view=net-7.0#fields) settings previously. So after https://github.com/actions/toolkit/pull/1373 it's possible to get this error if you have an open...

If v3.3.0 fails, then it is not related to the change above. What's the minimum workflow I can use to reproduce this? The following is not enough. ``` name: Test...

This issue is quite old, but to answer the question the expectation is that users use Git tags to utilize the action. The latest major release is `actions/checkout@v4`

v2 and v3 tags are updated to point to a release containing https://github.com/actions/checkout/pull/964. Please re-open if this did not address the problem.

I sent a [PR](https://github.com/actions/checkout/pull/1002) to fix an unrelated CI issue. In the meantime, could you please update the JS bundle with `npm run build`?

Sorry for the delay and bad info. I assumed this Action worked similarly to others owned by my team, but that doesn't seem to be the case. Instead of `npm...

Can you incorporate the fix from https://github.com/actions/checkout/pull/964 to address the merge conflict? Other than that LGTM.

Can you confirm what version of the Actions Runner you are using? Upgrading to Node 20 outside the runner is not enough. https://github.com/actions/runner/releases/tag/v2.308.0 is the minimum version to support Node...

`github.ref` is going to be the [fully formed ref](https://docs.github.com/en/actions/learn-github-actions/contexts#github-context:~:text=The%20fully%2Dformed%20ref%20of%20the%20branch%20or%20tag%20that%20triggered%20the%20workflow%20run.) that caused the workflow to run. If you want this to then checkout a tag, it would have to be a...