Rewa Wader
Rewa Wader
I'm not even using a seperate config file but I'm still getting the same error. I was not getting it previously.
From what I observed, the workflow reports are attached to the check run referring to the commit that is latest on the branch-from-which-workflow-has-run (in my case I'm using workflow_dispatch). I...
After tracing your code, the issue seems to have occurred at this step itself. Should I try giving a specific version like 20.x.x instead of just 20?
[https://nodejs.org/dist/index.json](https://nodejs.org/dist/index.json)
> I can ping `nodejs.org` from the runner's server and `curl https://nodejs.org/dist/index.json` returns correct results so I don't think it is a network issue. Yeah same in my case
> Maybe to avoid the merge commits you could try this in your workflow: > > 1. checkout production > 2. fetch main (origin) > 3. create a new local...
i'm getting the same for 3.9 on Debian 12😞
looks like issues aren't addressed :(
I already had a branch and wanted to create a pullrequest whose base will be the other branch which I had defined while calling this action. But what this action...
can you suggest me a workaround for above? @peter-evans